Query on SRB_FUNCTION_ABORT_COMMAND

NTDEV
1

Hi,
As part of storport miniport development I am implementing the handler
for SRB_FUNCTION_ABORT_COMMAND in the miniport driver. However, I did not
quite understand from the documentation under what scenarios does the
storport driver issue this SRB.
What would be a good way to test this code path in my driver and the
steps to trigger the port driver to issue this SRB? Will this SRB be issued
if an application with a pending overlapped read request is killed (as part
of IRP cancellation)? Alternatively, are there any tools from MS which could
be used here?

Regards,
Girish.

2

> steps to trigger the port driver to issue this SRB? Will this SRB be issued

if an application with a pending overlapped read request is killed (as part
of IRP cancellation)?

IIRC storage IRPs were never cancellable.

–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com

3

Thanks Maxim. So, I am still wondering if there is a way to test the abort
command code path from within my miniport driver.

I am thinking of writing an upper port filter driver (which would layer on
top of the port driver’s PDOs as well), issue an SRB containing a scsi_read
opcode from the filter driver and try to abort this request subsequently.
However, one thing I am not sure is if the storport would pass the request
with SRB_FUNCTION_ABORT_COMMAND as is to the miniport? Also, if there is an
alternate way to test/simulate this in a much more straightfoward way, it
would be helpful.

Regards,
Girish.

“Maxim S. Shatskih” wrote in message
news:xxxxx@ntdev…
> steps to trigger the port driver to issue this SRB? Will this SRB be
> issued
> if an application with a pending overlapped read request is killed (as
> part
> of IRP cancellation)?

IIRC storage IRPs were never cancellable.

–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com