NDIS ProtocolUnbindAdapterHandler Invoked On StandBy

[Le Chaud Lapin]

Hi All,

In my NDISPROT-based driver, NDIS invokes my
ProtocolUnbindAdapterHandler upon entering stand-by mode. Upon exiting
stand-by, a blocked overlapped-I/O ReadFile call fails with
GetLastError() returning ERROR_INVALID_HANDLE.

1. Is this normal behavior?
2. If this is normal behavior, what is the rationale? Where is the
documentation?

Under my model, a handle that is rendered invalid by I/O subsystem is
not a major concern, as I can simply re-establish all references, but
I would like to understand what's happening before proceeding.

TIA,

-Le Chaud Lapin-

[Le Chaud Lapin]

Post by Le Chaud Lapin
Hi All,
In my NDISPROT-based driver, NDIS invokes my
ProtocolUnbindAdapterHandler upon entering stand-by mode. Upon exiting
stand-by, a blocked overlapped-I/O ReadFile call fails with
GetLastError() returning ERROR_INVALID_HANDLE.
1. Is this normal behavior?
2. If this is normal behavior, what is the rationale? Where is the
documentation?
Under my model, a handle that is rendered invalid by I/O subsystem is
not a major concern, as I can simply re-establish all references, but
I would like to understand what's happening before proceeding.

Problem found.

NDISPROT was completing the ReadFile IRP with NtStatus ==
STATUS_INVALID_HANDLE, which, technically, is not true.

-Le Chaud Lapin-