Re: About the NEITHER method to read and write data
- From: soviet_bloke@xxxxxxxxxxx
- Date: 1 Oct 2006 14:38:35 -0700
Maxim,
The topmost driver which handles the NEITHER IOCTLs must be runned in the
same process as the user mode caller.
Actually, topmost drivers *ALWAYS* receive IOCTLs in context of threads
that initiate them - if thread context eventually gets lost, it
happens at some later stage
Anton Bassov
Maxim S. Shatskih wrote:
The topmost driver which handles the NEITHER IOCTLs must be runned in the
same process as the user mode caller.
In fact, NEITHER is of limited use, for FSCTLs mainly.
--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@xxxxxxxxxxxxxxxx
http://www.storagecraft.com
"jackie" <jackie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:FD463A35-DBA0-4BA0-9BA1-F6B7104521FC@xxxxxxxxxxxxxxxx
When reading the NEITHER method in WDM, it is wierd to me how it works.
ProbeForRead or ProbeForWrite can verifythat a range of address truly belongs
to user mode. But what if the process context is changed? Wouldn't writing
to the same address in another process context be something wrong?
--
Jackie
.
- References:
- Re: About the NEITHER method to read and write data
- From: Maxim S. Shatskih
- Re: About the NEITHER method to read and write data
- Prev by Date: Re: About the NEITHER method to read and write data
- Next by Date: Re: About the NEITHER method to read and write data
- Previous by thread: Re: About the NEITHER method to read and write data
- Next by thread: Re: UMDF for printer driver
- Index(es):
Relevant Pages
|
