Driver Problems? Questions? Issues?
Put OSR's experience to work for you! Contact us for assistance with:
  • Creating the right design for your requirements
  • Reviewing your existing driver code
  • Analyzing driver reliability/performance issues
  • Custom training mixed with consulting and focused directly on your specific areas of interest/concern.
Check us out. OSR, the Windows driver experts.

OSR Seminars

Go Back   OSR Online Lists > ntfsd
Welcome, Guest
You must login to post to this list
  Message 1 of 3  
07 Dec 17 12:16
Peter Scott
Join Date: 17 Feb 2012
Posts To This List: 686
Re[2]: Re[2]: How to filter the request in MUP?

Sorry if I missed something but how is your filter 'creating' a file object in pre-create? Are you saying that you call FltCreateFileEx() and this is the FO you are 'creating'? In your InstanceSetup callback, for network attachments (though not for every share), you'll see the VolumeDeviceType as FILE_DEVICE_NETWORK_FILE_SYSTEM and the VolumeFilesystemType as a network file system as in the FLT_FSTYPE_xxx types. Pete -- Kernel Drivers Windows File System and Device Driver Consulting 866.263.9295 ------ Original Message ------ From: "" <> To: "Windows File Systems Devs Interest List" <> Sent: 12/7/2017 9:53:29 AM Subject: RE:[ntfsd] Re[2]: How to filter the request in MUP? >I mean the file object indicated is not really created, my encryption >filter create a file object in the pre-create routine and just return >STATUS_SUCCESS to the upper driver. > >How to filter the network attachments in InstanceSetup callback, that's >exactly my question. > >--- >NTFSD is sponsored by OSR > <...excess quoted lines suppressed...>
  Message 2 of 3  
07 Dec 17 12:28
Hunter Wang
Join Date: 20 Mar 2017
Posts To This List: 9
Re[2]: Re[2]: How to filter the request in MUP?

Yes, my filter 'creating' a file object in pre-create with FltCreateFile(), so the FileObject upper driver wants to create just remains a pointer but not a real FileObject(created). The file object created by my filter is used to substitute for the FileObject(fake) in all of the callbacks such as IRP_MJ_SETXXX/IRP_MJ_READ/IRP_MJ_WRITE and so on, it works well. My filter used the same logic for the file stored in the network(\device\mup\test\ccedr.txt), my filter create a file object in the pre-create(so my filter should have attach to the mup device), but not catch the following requests(IRP_MJ_READ/IRP_MJ_WRITE/IRP_MJ_SETXXX...), so it get BSOD says the FileObject can not be resolved, if my filter catch the request and substitute the fake one, it should be okay.
  Message 3 of 3  
07 Dec 17 12:30
Hunter Wang
Join Date: 20 Mar 2017
Posts To This List: 9
Re[2]: Re[2]: How to filter the request in MUP?

I just don't understand why my filter can not catch the following request?
Posting Rules  
You may not post new threads
You may not post replies
You may not post attachments
You must login to OSR Online AND be a member of the ntfsd list to be able to post.

All times are GMT -5. The time now is 11:15.

Copyright ©2015, OSR Open Systems Resources, Inc.
Based on vBulletin Copyright ©2000 - 2005, Jelsoft Enterprises Ltd.
Modified under license