Filter manager does not attach to the mailslot (or named pipe) device
object. They don’t register as a file system.
The reason you are seeing mailslot names is because they can be accessed
remotely through LANMAN redirector.
The reason you get an error trying to get a normalized mailslot name is
because filter manager retrieves and error trying to do this.
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 Vossen, Joseph
(ISS Atlanta)
Sent: Monday, February 13, 2006 3:56 AM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] Mailslots and FltGetFileNameInformation()
Have you tried checking for FO_MAILSLOT in the FileObject Flags?
I never see this set for a file object that represents a mail slot. In
each case, the file object’s flag is 0x2.
It’s not clear if you’re trying to handle mailslots or avoid
them. If you want to avoid them completely, just check for
DEVICE_TYPE == FILE_DEVICE_MAILSLOT in your instance setup
and return STATUS_FLT_DO_NOT_ATTACH.
I’m trying to avoid them; thanks for reminding me that I have this info
at instance setup time. However, I never see this situation in my
instance setup routine. When I load my filter, I am invoked three (3)
times at my instance setup (automatic attachment) with the following
values:
DEVICE_TYPE FLT_FILE_SYSTEM_TYPE
FILE_DEVICE_NETWORK_FILE_SYSTEM (0x14) FLT_FSTYPE_WEBDAV (0x7)
FILE_DEVICE_NETWORK_FILE_SYSTEM (0x14) FLT_FSTYPE_LANMAN (0x6)
FILE_DEVICE_DISK_FILE_SYSTEM (0x8) FLT_FSTYPE_NTFS (0x2)
And my instance setup is never called again (i.e. I never receive an
instance setup callback where DEVICE_TYPE == FILE_DEVICE_MAILSLOT).
Thanks
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