Ken,
I have briefly analyzed your crash dump with deadlocked
FltSetInformationFile call. Well, although I found the deadlocked thread,
but I’m not THAT much familiar with fltmgr architecture to say what’s
wrong with it. Maybe others will:
THREAD 812a3020 Cid 370.380 Teb: 7ffdb000 Win32Thread: 00000000 WAIT: (Executive) KernelMode Non-Alertable
811506b8 SynchronizationEvent
IRP List:
f82dfe70: (0006,0190) Flags: 40000884 Mdl: 00000000
Not impersonating
Owning Process 812b8ae0 (VMWareService.exe)
Wait Start TickCount 10553 Elapsed Ticks: 14931
Context Switch Count 1002
UserTime 0:00:00.0000
KernelTime 0:00:00.0843
Start Address 0x7c57b700
Win32 Start Address 0x7c2dcf33
Stack Init f42cb000 Current f42ca63c Base f42cb000 Limit f42c8000 Call 0
Priority 15 BasePriority 15 PriorityDecrement 0 DecrementCount 0
ChildEBP RetAddr Args to Child
f42ca654 8042c2ad 00000000 f80f3e70 811506a8 nt!KiSwapThread+0xc5
f42ca67c f9d3c3f5 811506b8 00000000 00000000 nt!KeWaitForSingleObject+0x1a1
f42ca6b4 f9d3d393 f42ca6d4 00000103 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x235
f42ca6ec f9d4c075 8114c588 00000016 81139cc8 fltmgr!FltPerformSynchronousIo+0xa5
f42ca708 f3c79c24 8114c588 8113eca8 f42ca748 fltmgr!FltSetInformationFile+0x81
f42ca790 f9d534bd 8114e364 f42ca7dc f42ca7f8 fkdriver!FKDriverPreCreate+0x114
f42ca7bc f9d38941 00000009 00000000 f42ca7f8 fltmgr!FltvPreOperation+0x3d
f42ca820 f9d3c162 f42ca800 f42ca860 8114e308 fltmgr!FltpPerformPreCallbacks+0x24c
f42ca834 f9d47ec5 f42ca860 f9d47f67 00000000 fltmgr!FltpPassThroughInternal+0x30
f42ca848 f9d47e4d f42ca860 81138ea0 80064bec fltmgr!FltpCreateInternal+0x5f
f42ca87c 805290c4 81138ea0 f82dffdc f42cac48 fltmgr!FltpCreate+0x28b
f42ca8c8 804bf978 804824e0 804beeba f42cabcc nt!IovSpecialIrpCallDriver+0xcd
f42caa58 80450893 81800730 00000000 f42cab10 nt!IopParseDevice+0xabe
f42caad0 804d59a0 00000000 8181ed00 00000040 nt!ObpLookupObjectName+0x4e7
f42cabe0 8049f9f1 00000000 00000000 00000001 nt!ObOpenObjectByName+0xc8
f42cacbc 8049f596 00eef9dc 00100001 00eef980 nt!IopCreateFile+0x407
f42cad04 804a8279 00eef9dc 00100001 00eef980 nt!IoCreateFile+0x36
f42cad44 80464f84 00eef9dc 00100001 00eef980 nt!NtOpenFile+0x25
f42cad44 77f886b7 00eef9dc 00100001 00eef980 nt!KiSystemService+0xc4
00eef9d0 00000000 00000000 00000000 00000000 +0x77f886b7
L.
Yep, we found that, too. MS is looking into it.
Thanks for the effort!
Ken
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ladislav Zezula
Sent: Friday, November 11, 2005 7:59 AM
To: Windows File Systems Devs Interest List
Subject: Re: [ntfsd] FltSetInformationFile won’t rename a directory -
continued
Ken,
I have briefly analyzed your crash dump with deadlocked
FltSetInformationFile call. Well, although I found the deadlocked thread,
but I’m not THAT much familiar with fltmgr architecture to say what’s
wrong with it. Maybe others will:
THREAD 812a3020 Cid 370.380 Teb: 7ffdb000 Win32Thread: 00000000 WAIT:
(Executive) KernelMode Non-Alertable
811506b8 SynchronizationEvent
IRP List:
f82dfe70: (0006,0190) Flags: 40000884 Mdl: 00000000
Not impersonating
Owning Process 812b8ae0 (VMWareService.exe)
Wait Start TickCount 10553 Elapsed Ticks: 14931
Context Switch Count 1002
UserTime 0:00:00.0000
KernelTime 0:00:00.0843
Start Address 0x7c57b700
Win32 Start Address 0x7c2dcf33
Stack Init f42cb000 Current f42ca63c Base f42cb000 Limit f42c8000 Call 0
Priority 15 BasePriority 15 PriorityDecrement 0 DecrementCount 0
ChildEBP RetAddr Args to Child
f42ca654 8042c2ad 00000000 f80f3e70 811506a8 nt!KiSwapThread+0xc5
f42ca67c f9d3c3f5 811506b8 00000000 00000000 nt!KeWaitForSingleObject+0x1a1
f42ca6b4 f9d3d393 f42ca6d4 00000103 00000000
fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x235
f42ca6ec f9d4c075 8114c588 00000016 81139cc8
fltmgr!FltPerformSynchronousIo+0xa5
f42ca708 f3c79c24 8114c588 8113eca8 f42ca748
fltmgr!FltSetInformationFile+0x81
f42ca790 f9d534bd 8114e364 f42ca7dc f42ca7f8
fkdriver!FKDriverPreCreate+0x114
f42ca7bc f9d38941 00000009 00000000 f42ca7f8 fltmgr!FltvPreOperation+0x3d
f42ca820 f9d3c162 f42ca800 f42ca860 8114e308
fltmgr!FltpPerformPreCallbacks+0x24c
f42ca834 f9d47ec5 f42ca860 f9d47f67 00000000
fltmgr!FltpPassThroughInternal+0x30
f42ca848 f9d47e4d f42ca860 81138ea0 80064bec fltmgr!FltpCreateInternal+0x5f
f42ca87c 805290c4 81138ea0 f82dffdc f42cac48 fltmgr!FltpCreate+0x28b
f42ca8c8 804bf978 804824e0 804beeba f42cabcc nt!IovSpecialIrpCallDriver+0xcd
f42caa58 80450893 81800730 00000000 f42cab10 nt!IopParseDevice+0xabe
f42caad0 804d59a0 00000000 8181ed00 00000040 nt!ObpLookupObjectName+0x4e7
f42cabe0 8049f9f1 00000000 00000000 00000001 nt!ObOpenObjectByName+0xc8
f42cacbc 8049f596 00eef9dc 00100001 00eef980 nt!IopCreateFile+0x407
f42cad04 804a8279 00eef9dc 00100001 00eef980 nt!IoCreateFile+0x36
f42cad44 80464f84 00eef9dc 00100001 00eef980 nt!NtOpenFile+0x25
f42cad44 77f886b7 00eef9dc 00100001 00eef980 nt!KiSystemService+0xc4
00eef9d0 00000000 00000000 00000000 00000000 +0x77f886b7
L.
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