FltGetVolumeGuidName during InstanceSetup

OSR_Community_User · August 12, 2005, 12:02pm

I am calling FltGetVolumeGuidName from inside my InstanceSetupCallBack
routine yet it is hanging. This is a result of plugging in a USB drive. The
documentation says it is safe to call this routine during the
InstanceSetupCallBack.

The stack looks like this:

4.00002c 86fc1020 00053c1 Blocked nt!KiSwapContext+0x2e

nt!KiSwapThread+0x46

nt!KeWaitForSingleObject+0x1c2

MountMgr!MountMgrDeviceControl+0x2e

nt!IopfCallDriver+0x31

fltmgr!FltGetVolumeGuidName+0x13a

MyDriver!RepInstanceSetup+0xac

fltmgr!FltpDoInstanceSetupNotification+0x4b

fltmgr!FltpInitInstance+0x272

fltmgr!FltpCreateInstanceFromName+0x295

fltmgr!FltpEnumerateRegistryInstances+0xf4

fltmgr!FltpDoFilterNotificationForNewVolume+0xf5

fltmgr!FltpCreate+0x16a

nt!IopfCallDriver+0x31

naiavf5x+0x74a0

naiavf5x+0x2520

nt!IopfCallDriver+0x31

nt!IopParseDevice+0xa58

nt!ObpLookupObjectName+0x56a

nt!ObOpenObjectByName+0xeb

nt!IopCreateFile+0x407

nt!IoCreateFile+0x8e

nt!NtOpenFile+0x27

nt!KiFastCallEntry+0xf8

nt!ZwOpenFile+0x11

VolSnap!VspDeleteDiffAreaFilesWorker+0xa0

nt!IopProcessWorkItem+0x13

nt!ExpWorkerThread+0x100

nt!PspSystemThreadStartup+0x34

nt!KiThreadStartup+0x16

I was going to move the call when the first opened happened, but the docs
also say that that is when the InstanceSetupCallback is called. SO that
won’t help.

When can this routine safely be called?

Thanks,

Ken

OSR_Community_User · August 12, 2005, 12:21pm

> The documentation says it is safe to call this routine during the
InstanceSetupCallBack.

It is not safe. This was revealed at the last plugfest. You need to post
the query to a worker thread to the volume guid name without a deadlock.

It stinks, but that’s the way it is.

Dan.

At 09:01 AM 8/12/2005 -0700, you wrote:

I am calling FltGetVolumeGuidName from inside my InstanceSetupCallBack
routine yet it is hanging. This is a result of plugging in a USB drive.
The documentation says it is safe to call this routine during the
InstanceSetupCallBack.

The stack looks like this:

4.00002c 86fc1020 00053c1 Blocked nt!KiSwapContext+0x2e

nt!KiSwapThread+0x46

nt!KeWaitForSingleObject+0x1c2

MountMgr!MountMgrDeviceControl+0x2e

nt!IopfCallDriver+0x31

fltmgr!FltGetVolumeGuidName+0x13a

MyDriver!RepInstanceSetup+0xac

fltmgr!FltpDoInstanceSetupNotification+0x4b

fltmgr!FltpInitInstance+0x272

fltmgr!FltpCreateInstanceFromName+0x295

fltmgr!FltpEnumerateRegistryInstances+0xf4

fltmgr!FltpDoFilterNotificationForNewVolume+0xf5

fltmgr!FltpCreate+0x16a

nt!IopfCallDriver+0x31

naiavf5x+0x74a0

naiavf5x+0x2520

nt!IopfCallDriver+0x31

nt!IopParseDevice+0xa58

nt!ObpLookupObjectName+0x56a

nt!ObOpenObjectByName+0xeb

nt!IopCreateFile+0x407

nt!IoCreateFile+0x8e

nt!NtOpenFile+0x27

nt!KiFastCallEntry+0xf8

nt!ZwOpenFile+0x11

VolSnap!VspDeleteDiffAreaFilesWorker+0xa0

nt!IopProcessWorkItem+0x13

nt!ExpWorkerThread+0x100

nt!PspSystemThreadStartup+0x34

nt!KiThreadStartup+0x16

I was going to move the call when the first opened happened, but the docs
also say that that is when the InstanceSetupCallback is called. SO that
wont help.

When can this routine safely be called?

Thanks,

Ken

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

OSR_Community_User · August 22, 2005, 3:30pm

Hmm, what object (handle, fltinstance, device object etc) do you pass to the
worker thread to do this query?

Thanks,
Ken

-----Original Message-----
From: Dan Kyler [mailto:xxxxx@privtek.com]
Sent: Friday, August 12, 2005 12:21 PM
To: Windows File Systems Devs Interest List
Subject: Re: [ntfsd] FltGetVolumeGuidName during InstanceSetup

The documentation says it is safe to call this routine during the
InstanceSetupCallBack.

It is not safe. This was revealed at the last plugfest. You need to post
the query to a worker thread to the volume guid name without a deadlock.

It stinks, but that’s the way it is.

Dan.

At 09:01 AM 8/12/2005 -0700, you wrote:

I am calling FltGetVolumeGuidName from inside my InstanceSetupCallBack
routine yet it is hanging. This is a result of plugging in a USB drive.
The documentation says it is safe to call this routine during the
InstanceSetupCallBack.

The stack looks like this:

4.00002c 86fc1020 00053c1 Blocked nt!KiSwapContext+0x2e

nt!KiSwapThread+0x46

nt!KeWaitForSingleObject+0x1c2

MountMgr!MountMgrDeviceControl+0x2e

nt!IopfCallDriver+0x31

fltmgr!FltGetVolumeGuidName+0x13a

MyDriver!RepInstanceSetup+0xac

fltmgr!FltpDoInstanceSetupNotification+0x4b

fltmgr!FltpInitInstance+0x272

fltmgr!FltpCreateInstanceFromName+0x295

fltmgr!FltpEnumerateRegistryInstances+0xf4

fltmgr!FltpDoFilterNotificationForNewVolume+0xf5

fltmgr!FltpCreate+0x16a

nt!IopfCallDriver+0x31

naiavf5x+0x74a0

naiavf5x+0x2520

nt!IopfCallDriver+0x31

nt!IopParseDevice+0xa58

nt!ObpLookupObjectName+0x56a

nt!ObOpenObjectByName+0xeb

nt!IopCreateFile+0x407

nt!IoCreateFile+0x8e

nt!NtOpenFile+0x27

nt!KiFastCallEntry+0xf8

nt!ZwOpenFile+0x11

VolSnap!VspDeleteDiffAreaFilesWorker+0xa0

nt!IopProcessWorkItem+0x13

nt!ExpWorkerThread+0x100

nt!PspSystemThreadStartup+0x34

nt!KiThreadStartup+0x16

I was going to move the call when the first opened happened, but the docs
also say that that is when the InstanceSetupCallback is called. SO that
wont help.

When can this routine safely be called?

Thanks,

Ken

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@emc.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

OSR_Community_User · August 22, 2005, 4:23pm

I pass my instance context, which contains a pointer to the volume object.

Dan.

At 12:30 PM 8/22/2005 -0700, you wrote:

Hmm, what object (handle, fltinstance, device object etc) do you pass to
the worker thread to do this query?

Thanks,
Ken

-----Original Message-----
From: Dan Kyler [mailto:xxxxx mailto:xxxxx@privtek.com]
>Sent: Friday, August 12, 2005 12:21 PM
>To: Windows File Systems Devs Interest List
>Subject: Re: [ntfsd] FltGetVolumeGuidName during InstanceSetup
>
> > The documentation says it is safe to call this routine during the
>InstanceSetupCallBack.
>
>It is not safe. This was revealed at the last plugfest. You need to post
>the query to a worker thread to the volume guid name without a deadlock.
>
>It stinks, but that’s the way it is.
>
>- Dan.
>
>At 09:01 AM 8/12/2005 -0700, you wrote:
>
> >I am calling FltGetVolumeGuidName from inside my InstanceSetupCallBack
> >routine yet it is hanging. This is a result of plugging in a USB drive.
> >The documentation says it is safe to call this routine during the
> >InstanceSetupCallBack.
> >
> >
> >
> >The stack looks like this:
> >
> >
> >
> > 4.00002c 86fc1020 00053c1 Blocked nt!KiSwapContext+0x2e
> >
> > nt!KiSwapThread+0x46
> >
> > nt!KeWaitForSingleObject+0x1c2
> >
> >
> MountMgr!MountMgrDeviceControl+0x2e
> >
> > nt!IopfCallDriver+0x31
> >
> > fltmgr!FltGetVolumeGuidName+0x13a
> >
> > MyDriver!RepInstanceSetup+0xac
> >
> >
> >fltmgr!FltpDoInstanceSetupNotification+0x4b
> >
> > fltmgr!FltpInitInstance+0x272
> >
> >
> >fltmgr!FltpCreateInstanceFromName+0x295
> >
> >
> >fltmgr!FltpEnumerateRegistryInstances+0xf4
> >
> >
> >fltmgr!FltpDoFilterNotificationForNewVolume+0xf5
> >
> > fltmgr!FltpCreate+0x16a
> >
> > nt!IopfCallDriver+0x31
> >
> > naiavf5x+0x74a0
> >
> > naiavf5x+0x2520
> >
> > nt!IopfCallDriver+0x31
> >
> > nt!IopParseDevice+0xa58
> >
> > nt!ObpLookupObjectName+0x56a
> >
> > nt!ObOpenObjectByName+0xeb
> >
> > nt!IopCreateFile+0x407
> >
> > nt!IoCreateFile+0x8e
> >
> > nt!NtOpenFile+0x27
> >
> > nt!KiFastCallEntry+0xf8
> >
> > nt!ZwOpenFile+0x11
> >
> >
> >VolSnap!VspDeleteDiffAreaFilesWorker+0xa0
> >
> > nt!IopProcessWorkItem+0x13
> >
> > nt!ExpWorkerThread+0x100
> >
> > nt!PspSystemThreadStartup+0x34
> >
> > nt!KiThreadStartup+0x16
> >
> >
> >
> >I was going to move the call when the first opened happened, but the docs
> >also say that that is when the InstanceSetupCallback is called. SO that
> >wont help.
> >
> >
> >
> >When can this routine safely be called?
> >
> >
> >
> >Thanks,
> >
> >Ken
> >
> >—
> >Questions? First check the IFS FAQ at
> >https:https://www.osronline.com/ar
> ticle.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:https://www.osronline.com/article.cfm?id=17
>
>
>You are currently subscribed to ntfsd as: xxxxx@emc.com
>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: unknown lmsubst tag argument: ‘’
>To unsubscribe send a blank email to xxxxx@lists.osr.com</https:></https:></mailto:xxxxx>

OSR_Community_User · August 22, 2005, 4:47pm

Where volume object is “FltObjects->Volume”?

Are there any other query APIs that should not be called InstanceSetup?

Thanks,

Ken

From: Dan Kyler [mailto:xxxxx@privtek.com]
Sent: Monday, August 22, 2005 4:23 PM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] FltGetVolumeGuidName during InstanceSetup

I pass my instance context, which contains a pointer to the volume object.

Dan.

At 12:30 PM 8/22/2005 -0700, you wrote:

Hmm, what object (handle, fltinstance, device object etc) do you pass to the
worker thread to do this query?

Thanks,
Ken

-----Original Message-----
From: Dan Kyler [mailto:xxxxx@privtek.com mailto:xxxxx]
Sent: Friday, August 12, 2005 12:21 PM
To: Windows File Systems Devs Interest List
Subject: Re: [ntfsd] FltGetVolumeGuidName during InstanceSetup

> The documentation says it is safe to call this routine during the
InstanceSetupCallBack.

It is not safe. This was revealed at the last plugfest. You need to post
the query to a worker thread to the volume guid name without a deadlock.

It stinks, but that’s the way it is.

- Dan.

At 09:01 AM 8/12/2005 -0700, you wrote:

>I am calling FltGetVolumeGuidName from inside my InstanceSetupCallBack
>routine yet it is hanging. This is a result of plugging in a USB drive.
>The documentation says it is safe to call this routine during the
>InstanceSetupCallBack.
>
>
>
>The stack looks like this:
>
>
>
> 4.00002c 86fc1020 00053c1 Blocked nt!KiSwapContext+0x2e
>
> nt!KiSwapThread+0x46
>
> nt!KeWaitForSingleObject+0x1c2
>
>
MountMgr!MountMgrDeviceControl+0x2e
>
> nt!IopfCallDriver+0x31
>
> fltmgr!FltGetVolumeGuidName+0x13a
>
> MyDriver!RepInstanceSetup+0xac
>
>
>fltmgr!FltpDoInstanceSetupNotification+0x4b
>
> fltmgr!FltpInitInstance+0x272
>
>
>fltmgr!FltpCreateInstanceFromName+0x295
>
>
>fltmgr!FltpEnumerateRegistryInstances+0xf4
>
>
>fltmgr!FltpDoFilterNotificationForNewVolume+0xf5
>
> fltmgr!FltpCreate+0x16a
>
> nt!IopfCallDriver+0x31
>
> naiavf5x+0x74a0
>
> naiavf5x+0x2520
>
> nt!IopfCallDriver+0x31
>
> nt!IopParseDevice+0xa58
>
> nt!ObpLookupObjectName+0x56a
>
> nt!ObOpenObjectByName+0xeb
>
> nt!IopCreateFile+0x407
>
> nt!IoCreateFile+0x8e
>
> nt!NtOpenFile+0x27
>
> nt!KiFastCallEntry+0xf8
>
> nt!ZwOpenFile+0x11
>
>
>VolSnap!VspDeleteDiffAreaFilesWorker+0xa0
>
> nt!IopProcessWorkItem+0x13
>
> nt!ExpWorkerThread+0x100
>
> nt!PspSystemThreadStartup+0x34
>
> nt!KiThreadStartup+0x16
>
>
>
>I was going to move the call when the first opened happened, but the docs
>also say that that is when the InstanceSetupCallback is called. SO that
>wont help.
>
>
>
>When can this routine safely be called?
>
>
>
>Thanks,
>
>Ken
>
>—
>Questions? First check the IFS FAQ at
>https://www.osronline.com/article.cfm?id=17
https:
>
>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
https:

You are currently subscribed to ntfsd as: xxxxx@emc.com
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
https:

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@emc.com
To unsubscribe send a blank email to xxxxx@lists.osr.com</https:></https:></https:></mailto:xxxxx>

OSR_Community_User · August 23, 2005, 11:26am

At 01:46 PM 8/22/2005 -0700, you wrote:

Where volume object is FltObjects->Volume?

Yes.

Are there any other query APIs that should not be called InstanceSetup?

Anything that uses the mount manager can encounter this deadlock.

Dan.

Thanks,

Ken

From: Dan Kyler [mailto:xxxxx@privtek.com]
Sent: Monday, August 22, 2005 4:23 PM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] FltGetVolumeGuidName during InstanceSetup

I pass my instance context, which contains a pointer to the volume object.

Dan.

At 12:30 PM 8/22/2005 -0700, you wrote:

Hmm, what object (handle, fltinstance, device object etc) do you pass to
the worker thread to do this query?

Thanks,
Ken

-----Original Message-----
From: Dan Kyler [mailto:xxxxx mailto:xxxxx@privtek.com]
>Sent: Friday, August 12, 2005 12:21 PM
>To: Windows File Systems Devs Interest List
>Subject: Re: [ntfsd] FltGetVolumeGuidName during InstanceSetup
>
> > The documentation says it is safe to call this routine during the
>InstanceSetupCallBack.
>
>It is not safe. This was revealed at the last plugfest. You need to post
>the query to a worker thread to the volume guid name without a deadlock.
>
>It stinks, but that’s the way it is.
>
>- Dan.
>
>At 09:01 AM 8/12/2005 -0700, you wrote:
>
> >I am calling FltGetVolumeGuidName from inside my InstanceSetupCallBack
> >routine yet it is hanging. This is a result of plugging in a USB drive.
> >The documentation says it is safe to call this routine during the
> >InstanceSetupCallBack.
> >
> >
> >
> >The stack looks like this:
> >
> >
> >
> > 4.00002c 86fc1020 00053c1 Blocked nt!KiSwapContext+0x2e
> >
> > nt!KiSwapThread+0x46
> >
> > nt!KeWaitForSingleObject+0x1c2
> >
> >
> MountMgr!MountMgrDeviceControl+0x2e
> >
> > nt!IopfCallDriver+0x31
> >
> > fltmgr!FltGetVolumeGuidName+0x13a
> >
> > MyDriver!RepInstanceSetup+0xac
> >
> >
> >fltmgr!FltpDoInstanceSetupNotification+0x4b
> >
> > fltmgr!FltpInitInstance+0x272
> >
> >
> >fltmgr!FltpCreateInstanceFromName+0x295
> >
> >
> >fltmgr!FltpEnumerateRegistryInstances+0xf4
> >
> >
> >fltmgr!FltpDoFilterNotificationForNewVolume+0xf5
> >
> > fltmgr!FltpCreate+0x16a
> >
> > nt!IopfCallDriver+0x31
> >
> > naiavf5x+0x74a0
> >
> > naiavf5x+0x2520
> >
> > nt!IopfCallDriver+0x31
> >
> > nt!IopParseDevice+0xa58
> >
> > nt!ObpLookupObjectName+0x56a
> >
> > nt!ObOpenObjectByName+0xeb
> >
> > nt!IopCreateFile+0x407
> >
> > nt!IoCreateFile+0x8e
> >
> > nt!NtOpenFile+0x27
> >
> > nt!KiFastCallEntry+0xf8
> >
> > nt!ZwOpenFile+0x11
> >
> >
> >VolSnap!VspDeleteDiffAreaFilesWorker+0xa0
> >
> > nt!IopProcessWorkItem+0x13
> >
> > nt!ExpWorkerThread+0x100
> >
> > nt!PspSystemThreadStartup+0x34
> >
> > nt!KiThreadStartup+0x16
> >
> >
> >
> >I was going to move the call when the first opened happened, but the docs
> >also say that that is when the InstanceSetupCallback is called. SO that
> >wont help.
> >
> >
> >
> >When can this routine safely be called?
> >
> >
> >
> >Thanks,
> >
> >Ken
> >
> >—
> >Questions? First check the IFS FAQ at
> >https:https://www.osronline.com/ar
> ticle.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:https://www.osronline.com/article.cfm?id=17
>
>
>You are currently subscribed to ntfsd as: xxxxx@emc.com
>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: 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@emc.com
>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: unknown lmsubst tag argument: ‘’
>To unsubscribe send a blank email to xxxxx@lists.osr.com</https:></https:></mailto:xxxxx>

OSR_Community_User · August 23, 2005, 8:10pm

Thanks,

Which ones use the Mount Manager?

Ken

From: Dan Kyler [mailto:xxxxx@privtek.com]
Sent: Tuesday, August 23, 2005 11:26 AM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] FltGetVolumeGuidName during InstanceSetup

At 01:46 PM 8/22/2005 -0700, you wrote:

Where volume object is FltObjects->Volume?

Yes.

Are there any other query APIs that should not be called InstanceSetup?

Anything that uses the mount manager can encounter this deadlock.

Dan.

Thanks,

Ken

From: Dan Kyler [mailto:xxxxx@privtek.com mailto:xxxxx]
Sent: Monday, August 22, 2005 4:23 PM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] FltGetVolumeGuidName during InstanceSetup

I pass my instance context, which contains a pointer to the volume object.

- Dan.

At 12:30 PM 8/22/2005 -0700, you wrote:

Hmm, what object (handle, fltinstance, device object etc) do you pass to the
worker thread to do this query?

Thanks,
Ken

-----Original Message-----
From: Dan Kyler [mailto:xxxxx@privtek.com mailto:xxxxx]
Sent: Friday, August 12, 2005 12:21 PM
To: Windows File Systems Devs Interest List
Subject: Re: [ntfsd] FltGetVolumeGuidName during InstanceSetup

> The documentation says it is safe to call this routine during the
InstanceSetupCallBack.

It is not safe. This was revealed at the last plugfest. You need to post
the query to a worker thread to the volume guid name without a deadlock.

It stinks, but that’s the way it is.

- Dan.

At 09:01 AM 8/12/2005 -0700, you wrote:

>I am calling FltGetVolumeGuidName from inside my InstanceSetupCallBack
>routine yet it is hanging. This is a result of plugging in a USB drive.
>The documentation says it is safe to call this routine during the
>InstanceSetupCallBack.
>
>
>
>The stack looks like this:
>
>
>
> 4.00002c 86fc1020 00053c1 Blocked nt!KiSwapContext+0x2e
>
> nt!KiSwapThread+0x46
>
> nt!KeWaitForSingleObject+0x1c2
>
>
MountMgr!MountMgrDeviceControl+0x2e
>
> nt!IopfCallDriver+0x31
>
> fltmgr!FltGetVolumeGuidName+0x13a
>
> MyDriver!RepInstanceSetup+0xac
>
>
>fltmgr!FltpDoInstanceSetupNotification+0x4b
>
> fltmgr!FltpInitInstance+0x272
>
>
>fltmgr!FltpCreateInstanceFromName+0x295
>
>
>fltmgr!FltpEnumerateRegistryInstances+0xf4
>
>
>fltmgr!FltpDoFilterNotificationForNewVolume+0xf5
>
> fltmgr!FltpCreate+0x16a
>
> nt!IopfCallDriver+0x31
>
> naiavf5x+0x74a0
>
> naiavf5x+0x2520
>
> nt!IopfCallDriver+0x31
>
> nt!IopParseDevice+0xa58
>
> nt!ObpLookupObjectName+0x56a
>
> nt!ObOpenObjectByName+0xeb
>
> nt!IopCreateFile+0x407
>
> nt!IoCreateFile+0x8e
>
> nt!NtOpenFile+0x27
>
> nt!KiFastCallEntry+0xf8
>
> nt!ZwOpenFile+0x11
>
>
>VolSnap!VspDeleteDiffAreaFilesWorker+0xa0
>
> nt!IopProcessWorkItem+0x13
>
> nt!ExpWorkerThread+0x100
>
> nt!PspSystemThreadStartup+0x34
>
> nt!KiThreadStartup+0x16
>
>
>
>I was going to move the call when the first opened happened, but the docs
>also say that that is when the InstanceSetupCallback is called. SO that
>wont help.
>
>
>
>When can this routine safely be called?
>
>
>
>Thanks,
>
>Ken
>
>—
>Questions? First check the IFS FAQ at
>https://www.osronline.com/article.cfm?id=17
https:
>
>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
https:

You are currently subscribed to ntfsd as: xxxxx@emc.com
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
https:

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
https:

You are currently subscribed to ntfsd as: xxxxx@emc.com
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
https:

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@emc.com
To unsubscribe send a blank email to xxxxx@lists.osr.com</https:></https:></https:></https:></https:></mailto:xxxxx></mailto:xxxxx>