Peter
Mon Feb 14 13:04:49 CST 2005
You can check the RequestorMode flag in the IRP to see the mode of the
request's initiator.
User-mode initiators will have UserMode set in this value. Kernel-mode
components can choose which mode they want set depending on the behavior
they want from the lower stack.
It is not an essential thing to know which module is asking you to do the
work - if you find that it is you should revisit your design. Drivers
shouldn't care what component is sending them I/O. They may need to know
attributes of the caller (e.g. its execution mode, whether it's a 32-bit or
64-bit process, its security context, etc...) and these are generally
documented and passed to the driver.
-p
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Andreas Winter" <andreas_winter@sonydadc.com> wrote in message
news:ugc0xcnEFHA.392@TK2MSFTNGP14.phx.gbl...
> I'm still a beginner in driver programming and want to learn how things
> are working in detail. This question about the originator came me when I
> was analysing the driver stack and IRP flow down and up.
>
> Generally, I think in kernel there should not be too/so much secrets or
> undocumented things, because they misguide to do them anyway.
>
> I think it is or should be an essential thing to know which user/kernel
> mode modul wants me as a driver to do anything by sending me IRPs.
>
> Andreas.
>
> Peter Wieland [MSFT] schrieb:
>> surprisingly no one has asked this yet:
>>
>> why would you want to do this?
>>
>> -p
>>