If I call GetFltInstanceInformation asking for InstanceFullInformation
(INSTANCE_FULL_INFORMATION) during the InstanceSetup call back.
Is it possilble to hang the system due to the Mount Manager bug since
FULL_INFO contains the volume name?
Or is it only a problem if you query for drive letter or guid name (i.e.
a direct query to the mountmgr).
I seem to remember Flt GetVolumeName one of the functions that could not
be called.
Thanks,
Ken
Hi!
The name, that FltGetVolumeName returns is always the “RealDeviceName”, isn’t it?
wrote news:xxxxx@ntfsd…
If I call GetFltInstanceInformation asking for InstanceFullInformation (INSTANCE_FULL_INFORMATION) during the InstanceSetup call back.
Is it possilble to hang the system due to the Mount Manager bug since FULL_INFO contains the volume name?
Or is it only a problem if you query for drive letter or guid name (i.e. a direct query to the mountmgr).
I seem to remember Flt GetVolumeName one of the functions that could not be called.
Thanks,
Ken
I don’t know if it is the “real device name” or not. My concern and
question is will it query the mount manager to get it while in the
instance setup?
Thanks,
Ken
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of frank
Sent: Thursday, May 08, 2008 4:02 AM
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] GetFltInstanceInformation during InstanceSetup
Hi!
The name, that FltGetVolumeName returns is always the “RealDeviceName”,
isn’t it?
wrote news:xxxxx@ntfsd…
If I call GetFltInstanceInformation asking for
InstanceFullInformation (INSTANCE_FULL_INFORMATION) during the
InstanceSetup call back.
Is it possilble to hang the system due to the Mount Manager bug
since FULL_INFO contains the volume name?
Or is it only a problem if you query for drive letter or guid
name (i.e. a direct query to the mountmgr).
I seem to remember Flt GetVolumeName one of the functions that
could not be called.
Thanks,
Ken
—
NTFSD is sponsored by OSR
For our schedule debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars
You are currently subscribed to ntfsd as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
I don’t think, that FltGetXXXX will send IRPs, unlike FltQueryXXXXX.
I have an “InstanceSetup” routine in my driver calling “FltGetVolumeInformation” and this has never been a problem.
schrieb im Newsbeitrag news:xxxxx@ntfsd…
I don’t know if it is the “real device name” or not. My concern and question is will it query the mount manager to get it while in the instance setup?
Thanks,
Ken
------------------------------------------------------------------------------
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of frank
Sent: Thursday, May 08, 2008 4:02 AM
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] GetFltInstanceInformation during InstanceSetup
Hi!
The name, that FltGetVolumeName returns is always the “RealDeviceName”, isn’t it?
wrote news:xxxxx@ntfsd…
If I call GetFltInstanceInformation asking for InstanceFullInformation (INSTANCE_FULL_INFORMATION) during the InstanceSetup call back.
Is it possilble to hang the system due to the Mount Manager bug since FULL_INFO contains the volume name?
Or is it only a problem if you query for drive letter or guid name (i.e. a direct query to the mountmgr).
I seem to remember Flt GetVolumeName one of the functions that could not be called.
Thanks,
Ken
—
NTFSD is sponsored by OSR
For our schedule debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars
You are currently subscribed to ntfsd as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
FltGetInstanceInformation with INSTANCE_FULL_INFORMATION won’t generate a direct call to the mount manager. Should be safe to call once you get the instance pointer.
Regards,
Alex.
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 frank
Sent: Thursday, May 08, 2008 8:31 AM
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] GetFltInstanceInformation during InstanceSetup
I don’t think, that FltGetXXXX will send IRPs, unlike FltQueryXXXXX.
I have an “InstanceSetup” routine in my driver calling “FltGetVolumeInformation” and this has never been a problem.
> schrieb im Newsbeitrag news:xxxxx@ntfsd…
I don’t know if it is the “real device name” or not. My concern and question is will it query the mount manager to get it while in the instance setup?
Thanks,
Ken
________________________________
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of frank
Sent: Thursday, May 08, 2008 4:02 AM
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] GetFltInstanceInformation during InstanceSetup
Hi!
The name, that FltGetVolumeName returns is always the “RealDeviceName”, isn’t it?
> wrote news:xxxxx@ntfsd…
If I call GetFltInstanceInformation asking for InstanceFullInformation (INSTANCE_FULL_INFORMATION) during the InstanceSetup call back.
Is it possilble to hang the system due to the Mount Manager bug since FULL_INFO contains the volume name?
Or is it only a problem if you query for drive letter or guid name (i.e. a direct query to the mountmgr).
I seem to remember Flt GetVolumeName one of the functions that could not be called.
Thanks,
Ken
—
NTFSD is sponsored by OSR
For our schedule debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars
You are currently subscribed to ntfsd as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
NTFSD is sponsored by OSR
For our schedule debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars
You are currently subscribed to ntfsd as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com