Fast I/O Query Open?

Hi all:

It appears that the FastIoQueryOpen routine is the only one that takes an
IRP instead of a FileObject. As far as I can tell, though, all this routine
will do is use the IRP to get to the FileObject, to get to the file name.
It will use this to fill the NetworkInformation buffer fields before
returning.

Does anyone know why this routine takes an IRP instead of a FileObject? Is
the FSD expected to use any other information in the IRP except for the
FileObject’s file name?

Thanks,
Curt

Curt,

The IRP in question is an IRP_MJ_CREATE. Thus, in theory, the file system
can perform whatever validation is necessary to process the create. This
could include, for instance, a complete security check.

If all your FSD wants is the file name, by all means just use that.

Regards,

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com http:

-----Original Message-----
From: xxxxx@omnishift.com [mailto:xxxxx@omnishift.com]
Sent: Wednesday, July 05, 2000 1:10 PM
To: File Systems Developers
Subject: [ntfsd] Fast I/O Query Open?

Hi all:

It appears that the FastIoQueryOpen routine is the only one that takes an
IRP instead of a FileObject. As far as I can tell, though, all this routine
will do is use the IRP to get to the FileObject, to get to the file name.
It will use this to fill the NetworkInformation buffer fields before
returning.

Does anyone know why this routine takes an IRP instead of a FileObject? Is
the FSD expected to use any other information in the IRP except for the
FileObject’s file name?

Thanks,
Curt</http:>

Fast I/O Query Open?>Does anyone know why this routine takes an IRP instead
of a FileObject? Is

the FSD expected to use any other information in the IRP except for the

AFAIK it is called from IopParseDevice in case of query-only open.
The IRP is the correctly formed CREATE IRP.

Max