Completion Routine Not Called

NTFSD
1

Hi,

Problem:
Upper driver Completion routine not
getting called, though Lower driver
completes the Irp.

In our scenario, Upper driver is not
attached over lower driver. We get
the device object pointer, set
the completion routine and send
the Irp through Iocalldriver call.

I would like to know, if a driver
registers a completion routine
for a asynchronous Irp, should it
be (the originator of the Irp)
attached to the device stack so that
its completion routine is called.
Is it mandatory to attach over
device stack so that completion
routine gets called from IoManager.

Thanks,
Priya.

2

It would be nice if you provide some piece of your code. How do you allocate
IRP and how do you set up your completion routine?

----- Original Message -----
From: “priya”
To: “File Systems Developers”
Sent: Tuesday, January 07, 2003 2:31 PM
Subject: [ntfsd] Completion Routine Not Called

> Hi,
>
> Problem:
> Upper driver Completion routine not
> getting called, though Lower driver
> completes the Irp.
>
> In our scenario, Upper driver is not
> attached over lower driver. We get
> the device object pointer, set
> the completion routine and send
> the Irp through Iocalldriver call.
>
>
> I would like to know, if a driver
> registers a completion routine
> for a asynchronous Irp, should it
> be (the originator of the Irp)
> attached to the device stack so that
> its completion routine is called.
> Is it mandatory to attach over
> device stack so that completion
> routine gets called from IoManager.
>
> Thanks,
> Priya.
>
>
>
>
>
> —
> You are currently subscribed to ntfsd as: xxxxx@vba.com.by
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>