For Volume Open
- (FileObject->Flags & FO_VOLUME_OPEN) = TRUE
OR - (FileObject->FileName.Length = 0) AND (FileObject->RelatedFileObject = NULL)
in the filter i always see the 2nd condition. when does 1st condition occur.
For some unknown reason the IOManager sets the FO_VOLUME_OPEN flag AFTER the create has completed. This means it will be set for all other operations (besides create) to this file object.
I was so tired of dealing with this I modified the filter manager to set this flag before it sends pre-create operations to minifilters. This means a minifilter will see it correctly set for ALL operations.
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: Wednesday, June 29, 2005 5:25 AM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] Volume Open & FO_VOLUME_OPEN
For Volume Open
- (FileObject->Flags & FO_VOLUME_OPEN) = TRUE
OR - (FileObject->FileName.Length = 0) AND (FileObject->RelatedFileObject = NULL)
?
?
in the filter i always see the 2nd condition. when does 1st condition occur.
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
Thank you.
By saying “AFTER the create has completed” you mean to say the flag is not
set even in “Post-Create”?
“Neal Christiansen” wrote in message
news:xxxxx@ntfsd…
For some unknown reason the IOManager sets the FO_VOLUME_OPEN flag AFTER the
create has completed. This means it will be set for all other operations
(besides create) to this file object.
I was so tired of dealing with this I modified the filter manager to set
this flag before it sends pre-create operations to minifilters. This means
a minifilter will see it correctly set for ALL operations.
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: Wednesday, June 29, 2005 5:25 AM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] Volume Open & FO_VOLUME_OPEN
For Volume Open
1. (FileObject->Flags & FO_VOLUME_OPEN) = TRUE
OR
2. (FileObject->FileName.Length = 0) AND (FileObject->RelatedFileObject =
NULL)
in the filter i always see the 2nd condition. when does 1st condition occur.
—
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
How about “after the create has been completed by the underlying file
system driver”. It wouldn’t be set after completion by a driver BELOW
the file system driver (if such a call is made) but would be set after
completion by the file system driver.
If you are a file system filter, you would observe the bit set.
Regards,
Tony
Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Mani
Sent: Friday, July 01, 2005 9:12 AM
To: ntfsd redirect
Subject: Re:[ntfsd] Volume Open & FO_VOLUME_OPEN
Thank you.
By saying “AFTER the create has completed” you mean to say the flag is
not
set even in “Post-Create”?
“Neal Christiansen” wrote in message
news:xxxxx@ntfsd…
For some unknown reason the IOManager sets the FO_VOLUME_OPEN flag AFTER
the
create has completed. This means it will be set for all other
operations
(besides create) to this file object.
I was so tired of dealing with this I modified the filter manager to set
this flag before it sends pre-create operations to minifilters. This
means
a minifilter will see it correctly set for ALL operations.
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: Wednesday, June 29, 2005 5:25 AM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] Volume Open & FO_VOLUME_OPEN
For Volume Open
1. (FileObject->Flags & FO_VOLUME_OPEN) = TRUE
OR
2. (FileObject->FileName.Length = 0) AND (FileObject->RelatedFileObject
=
NULL)
in the filter i always see the 2nd condition. when does 1st condition
occur.
—
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
—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17
You are currently subscribed to ntfsd as: xxxxx@osr.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
I am not seeing the bit set in Post Create.
“Tony Mason” wrote in message news:xxxxx@ntfsd…
How about “after the create has been completed by the underlying file
system driver”. It wouldn’t be set after completion by a driver BELOW
the file system driver (if such a call is made) but would be set after
completion by the file system driver.
If you are a file system filter, you would observe the bit set.
Regards,
Tony
Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Mani
Sent: Friday, July 01, 2005 9:12 AM
To: ntfsd redirect
Subject: Re:[ntfsd] Volume Open & FO_VOLUME_OPEN
Thank you.
By saying “AFTER the create has completed” you mean to say the flag is
not
set even in “Post-Create”?
“Neal Christiansen” wrote in message
news:xxxxx@ntfsd…
For some unknown reason the IOManager sets the FO_VOLUME_OPEN flag AFTER
the
create has completed. This means it will be set for all other
operations
(besides create) to this file object.
I was so tired of dealing with this I modified the filter manager to set
this flag before it sends pre-create operations to minifilters. This
means
a minifilter will see it correctly set for ALL operations.
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: Wednesday, June 29, 2005 5:25 AM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] Volume Open & FO_VOLUME_OPEN
For Volume Open
1. (FileObject->Flags & FO_VOLUME_OPEN) = TRUE
OR
2. (FileObject->FileName.Length = 0) AND (FileObject->RelatedFileObject
=
NULL)
in the filter i always see the 2nd condition. when does 1st condition
occur.
—
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
—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17
You are currently subscribed to ntfsd as: xxxxx@osr.com
To unsubscribe send a blank email to xxxxx@lists.osr.com