FileSpy comment in SpyCommonDeviceIoControl-
“When the FASTIO path is called, the IO Manager has not done the work to buffer the input buffer, output buffer or both buffers (as specified by the IOCTL definition).”
does this mean the buffers are not mapped in system address space.
Yes, that is exactly what it means.
Ravi Pudipeddi and Tony Mason very recently commented on this exact thing. All buffers in ALL FastIo operations must be accessed as METHOD_NEITHER buffers. This is why it was suggested that you always return FALSE from this FAST IO operation and process it as an IRP. It will be simpler to handle.
Please read the recent archives.
Neal Christiansen
Microsoft File System Filter Group Lead
This posting is provided “AS IS” with no warranties, and confers no Rights
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Mani
Sent: Friday, June 03, 2005 1:45 AM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] SpyCommonDeviceIoControl
Questions? First check the IFS FAQ at https://www.osronline.com/article.cfm?id=17
You are currently subscribed to ntfsd as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com