Re: What's the secmantics of IoDetachDevice?
- From: "Maxim S. Shatskih" <maxim@xxxxxxxxxxxxxxxx>
- Date: Fri, 10 Aug 2007 23:42:42 +0400
C's driver will have its FastIoDetachDevice callback called (if it exists),
and should detach and destroy C in this callback.
For WDM PnP stacks, this is not interesting - the MN_REMOVE_DEVICE path
should detach and destroy the device objects from bottom to top, nobody will
destroy in the middle.
--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@xxxxxxxxxxxxxxxx
http://www.storagecraft.com
"xmllmx" <xmllmx@xxxxxxxxx> wrote in message
news:1186734780.536393.196570@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
The DDK documentation on IoDetachDevice is terribly concise.
Suppose I have a filter A wanting to attach to device object B, and I
attached A to B successfully. Later, another filter C attach itself to
A, so C->A->B make up a device stack. If filter A calls
IoDetachDevice(pDeviceB); then A is sure to be removed from the stack.
However, the question is: Is C still on the top of the stack? (i.e C-
B?)
.
- References:
- What's the secmantics of IoDetachDevice?
- From: xmllmx
- What's the secmantics of IoDetachDevice?
- Prev by Date: 32-bit ClassInstall for 64-bit driver
- Next by Date: Re: What's the secmantics of IoDetachDevice?
- Previous by thread: What's the secmantics of IoDetachDevice?
- Next by thread: Re: What's the secmantics of IoDetachDevice?
- Index(es):
Relevant Pages
|
|