FileSpy.sys incorrectly logs errorneous Fast IO operations

NTFSD
1

Hi, all

I found a bug in the FileSpy code.
If a FastIO operations ends with failure (i.e. if the underlying
filter/FSD returns FALSE), FileSpy logs the IoStatus
as if it has been filled. But the IoStatus is filled only in the case
of success, isn’t it ?

The result of this is that the log entries contain
garbage values.

See the SpyFastIoRead - the underlying driver is called,
then (regardless of the return value) the IoStatus is logged.

L.

2

Ladislav,

Thank you for pointing this out. You are correct; this is definitely a
bug in FileSpy. Note that it is not limited to READ. All FastIo
operations that have an IoStatus parameter have this wrong.

It may be too late to get this fixed in the Srv03 SP1 IFSKit but I will
try.

Neal Christiansen
Microsoft File System Filter Group Lead
This posting is provided “AS IS” with no warranties, and confers no
rights

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ladislav Zezula
Sent: Tuesday, January 11, 2005 12:32 AM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] FileSpy.sys incorrectly logs errorneous Fast IO
operations

Hi, all

I found a bug in the FileSpy code.
If a FastIO operations ends with failure (i.e. if the underlying
filter/FSD returns FALSE), FileSpy logs the IoStatus
as if it has been filled. But the IoStatus is filled only in the case
of success, isn’t it ?

The result of this is that the log entries contain
garbage values.

See the SpyFastIoRead - the underlying driver is called,
then (regardless of the return value) the IoStatus is logged.

L.

Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com