Correct. Looks like, the thumb rule is, unless you allocate an Irp, you
don’t free it.
-----Original Message-----
From: Justin Frodsham [mailto:zeppelin@io.com]
Sent: Tuesday, October 15, 2002 4:18 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Question about IoBuildDeviceIoControlRequest ;
Please Ignore the first message uncompleted
I paused on that too and came to the conclusion that the lower driver
you
are passing the Irp to will call IoCompleteRequest. Since this is going
to
happen you do not manually free the Irp. Rather the call to
IoCompleteRequest by the lower driver does the cleanup.
-Justin
At 07:29 AM 10/15/2002, you wrote:
Hi all,
I have a little doubt about IoBuildDeviceIoControl Request .
In DDK documentation , it says
"IRPs created using IoBuildDeviceIoControlRequest must be completed by
calling IoCompleteRequest and not by merely deallocating the IRP with
IoFreeIrp. "But when I checked the sample code in DDK , none of the samples either
frees the IRP or completes the IRP .In DDK documentation , it says
“IoBuildDeviceIoControlRequest queues the IRPs it creates in the IRP
queue of the current thread.”Is that means the current thread completes the IRP and releases the
memory ?Thanks
srinivasa
You are currently subscribed to ntdev as: zeppelin@io.com
To unsubscribe send a blank email to %%email.unsub%%
You are currently subscribed to ntdev as: chakradhar.kommuri@hp.com To
unsubscribe send a blank email to %%email.unsub%%