Hi,
I’m writing a filter driver that needs to pend some IRPs. When i
determine that i need to pend an Irp i call IoMarkIrpPending(pIrp),
return STATUS_PENDING and notify another process that i need data to
proceed.
When i get a message with the data that i need to continue, i try to do
so by calling IoCallDriver( deviceExtension->NextDriverDeviceObject,
pIrp) as i would have done if i had not pended the irp.
I’m not exactly sure whats happening after i do this but it isnt good.
I have the feeling i’m on the wrong track. Am i approaching this properly?
Thanks,
Aaron
If you have real work for driver under your filter driver stack to do, you
should call IoCallDriver, with completion routine set. Otherwise, make sure
you release resources grabbed for this op and call IoCompleteRequest.
Bi
-----Original Message-----
From: a a r o n [mailto:xxxxx@outerbody.com]
Sent: Wednesday, November 13, 2002 1:31 PM
To: File Systems Developers
Subject: [ntfsd] IoUnMarkIrpPending()
Hi,
I’m writing a filter driver that needs to pend some IRPs. When i
determine that i need to pend an Irp i call IoMarkIrpPending(pIrp),
return STATUS_PENDING and notify another process that i need data to
proceed.
When i get a message with the data that i need to continue, i try to do
so by calling IoCallDriver( deviceExtension->NextDriverDeviceObject,
pIrp) as i would have done if i had not pended the irp.
I’m not exactly sure whats happening after i do this but it isnt good.
I have the feeling i’m on the wrong track. Am i approaching this properly?
Thanks,
Aaron
You are currently subscribed to ntfsd as: xxxxx@appstream.com
To unsubscribe send a blank email to %%email.unsub%%