Tony:
Does this mean that NTFS will setup Vpb differently? I thought that seting
up
FileObject->Vpb pointer is a “fixed” part of create routine for each and
every
file system driver.
Regards,
Vladimir
-----Original Message-----
From: Tony Mason [mailto:xxxxx@osr.com]
Sent: Tuesday, August 20, 2002 7:04 AM
To: File Systems Developers
Subject: [ntfsd] RE: Shadow device object only “works” for IRP_MJ_CREATE
FAT will still set up the FileObject->Vpb pointer for the shadow file
object. You will need to handle that as appropriate in your filter driver.
Regards,
Tony
Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com
Hope to see you at the next OSR file systems class in San Jose, CA September
16, 2002!
-----Original Message-----
From: Bartjan Wattel [mailto:xxxxx@zeelandnet.nl]
Sent: Tuesday, August 20, 2002 9:34 AM
To: File Systems Developers
Subject: [ntfsd] Shadow device object only “works” for IRP_MJ_CREATE
Hi guys,
I have successfully implemented the ‘shadow device’ feature for getting
rid of reentrancy problems. The shadow device stuff is working perfectly
for file/directory open/create calls, however, calls to ZwClose and
other Zw* functions still seem to enter my dispatch routine via the main
device objects, rather than via the shadow device objects. Since I’m
looking at IRP_MJ_CLEANUP and IRP_MJ_CLOSE, this still hangs up my
driver.
What is the solution to get around this ? Rolling my own
read/write/queryinfo/close IRPs ?
Best,
Bartjan.
You are currently subscribed to ntfsd as: xxxxx@osr.com
To unsubscribe send a blank email to %%email.unsub%%
You are currently subscribed to ntfsd as: xxxxx@Starbase.com
To unsubscribe send a blank email to %%email.unsub%%