No, it cannot (and if the sender is using these fields, it has a bug).
This is only of the field that are reserved for the ownder of the irp,
where owner is the current driver which has the IRP pended. Basically,
the rules that apply to Tail.Overlay.DriverContext apply to
Tail.Overlay.ListEntry.
d
-----Original Message-----
From: Deevi, Srinivasa [mailto:xxxxx@microtune.com]
Sent: Wednesday, August 14, 2002 12:36 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Which is the best way to implement Driver managed
Queues ?
Hi Peter
"You may only use it while you own the IRP in your driver. "
Does this mean when the IRP reaches our driver layer , even though our
driver does not create the IRP ?
Is there anyway , some driver could be using Tail.Overlay.ListEntry
variable and still passing down to next level layer ? Any example ?
Thanks in advance
srinivasa
-----Original Message-----
From: Peter Viscarola [mailto:xxxxx@osr.com]
Sent: Wednesday, August 14, 2002 11:04 AM
To: NT Developers Interest List
Subject: [ntdev] Re: Which is the best way to implement Driver managed
Queues ?
“Deevi, Srinivasa” wrote in message
news:xxxxx@ntdev…
>
> . Is it good to do this way ? Can we use the ListEntry variable in
> IRP in any layer where the IRP would be kept pended ?
>
Yes. Tail.Overlay.ListEntry is there precisely for this purpose. You
may only use it while you own the IRP in your driver. If you pass the
IRP down the stack and get it back, you should expect the contents of
this location to have changed.
Chris Dore" wrote in message
news:xxxxx@ntdev…>
> You also have “Cancel-Safe IRP Queues” available to you, they are in
> the
DDK
> but don’t get used in too many of the samples…yet.
>
I’d strongly recommend you investigate the use of the IoCsqXxxx
functions in the DDK. They are no more difficult to use than setting up
your own queues, and they can simplify cancel handling enormously.
They’re trivial to implement – There’s an easy to understand sample
provided in the ddk \ddk\src\general\cancel…
Peter
OSR
—
You are currently subscribed to ntdev as: xxxxx@microtune.com
To unsubscribe send a blank email to %%email.unsub%%
—
You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to %%email.unsub%%