my minifilter project works well in all environment,excepte that:
When SRV is linux samba,the RDR is on the winXP.
When I call FltCancelFileOpen in postcreate,the system will crash.
there is a thread in this lists,but on answer.
http://www.osronline.com/showThread.cfm?link=116096
Anybody can clear it?
I think it is a bug from microsoft…
Wow, this is definitely a Microsoft bug, this is like the hundredth time
I’ve seen it.
Kinda makes you want to install Ubuntu doesn’t it…
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@hotmail.com
Sent: Monday, April 06, 2009 3:21 AM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] Call FltCancelFileOpen when SRV is samba,system crash.MS
bug?
my minifilter project works well in all environment,excepte that:
When SRV is linux samba,the RDR is on the winXP.
When I call FltCancelFileOpen in postcreate,the system will crash.
there is a thread in this lists,but on answer.
http://www.osronline.com/showThread.cfm?link=116096
Anybody can clear it?
I think it is a bug from microsoft…
NTFSD is sponsored by OSR
For our schedule of debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
microsoft can’t fix it?
no hotfix for it?
tragedy!
Neither the thread to which you point, nor your thread indicate what the
actual failure is - I don’t know how anyone can fix something at this
point.
I’ve had similar failures, but without seeing detailed information I’m
not going to point to solutions for those failures, as they are fairly
technical in nature (and the resolution to one is deeply ugly, the other
is a non-public hot-fix that requires you go to Microsoft support to
obtain.)
Of course, from Microsoft’s perspective, you’ve yet to demonstrate a bug
in Windows - this only happens when you use your filter, and it only
happens when you are using a non-Microsoft SMB server. Without detailed
analysis and someone explaining what happened, and why this is a Windows
issue, I can’t see this getting fixed.
Tony
OSR
Apparently it’s impossible to win anything against Tony…
I tried and was succeeding, until this…
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tony Mason
Sent: Monday, April 06, 2009 7:16 AM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] Call FltCancelFileOpen when SRV is samba,system
crash.MS bug?
Neither the thread to which you point, nor your thread indicate what the
actual failure is - I don’t know how anyone can fix something at this
point.
I’ve had similar failures, but without seeing detailed information I’m
not going to point to solutions for those failures, as they are fairly
technical in nature (and the resolution to one is deeply ugly, the other
is a non-public hot-fix that requires you go to Microsoft support to
obtain.)
Of course, from Microsoft’s perspective, you’ve yet to demonstrate a bug
in Windows - this only happens when you use your filter, and it only
happens when you are using a non-Microsoft SMB server. Without detailed
analysis and someone explaining what happened, and why this is a Windows
issue, I can’t see this getting fixed.
Tony
OSR
NTFSD is sponsored by OSR
For our schedule of debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
1st,this should be a bug in microsoft,I think.
In win2K rollup 1,everything is OK.
In winxp sp1,sp2,it will crash.But in winxp sp3,everything is OK.
I don’t test win2K3,but I think sp2 should be OK.
In vista,everything is OK.
In winxp sp2,the details about the crash:
1.the IRP_MJ_CREATE for opening \192.168.1.1\test\1.txt ,is coming.
2.in the postcreate,I call FltCancelFileOpen,and set ACCESS_DENY.
everything is OK.
3.But if I returned in my postcreate,the system crash:
DFS_FILE_SYSTEM (82)
Arguments:
Arg1: f96b0ea2
Arg2: f96af93f
Arg3: 00000000
Arg4: 00000000
PEB is paged out (Peb.Ldr = 7ffde00c). Type “.hh dbgerr001” for details
PEB is paged out (Peb.Ldr = 7ffde00c). Type “.hh dbgerr001” for details
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x82
PROCESS_NAME: explorer.exe
LAST_CONTROL_TRANSFER: from f96b729c to 804f9925
STACK_TEXT:
f79b38e4 f96b729c 00000082 f96b0ea2 f96af93f nt!KeBugCheckEx+0x1b
f79b3908 f96b0ea2 81585a18 81585b08 ff723cb8 Mup!DfsBugCheck+0x2a
f79b3944 f96af93f 8143e310 81585a08 81585a18 Mup!DfsCommonClose+0x4f
f79b3988 f96afaac 8172ec88 81585a08 81585a18 Mup!DfsFsdClose+0xf8
f79b39d4 804eedf9 8172ec88 81585a08 81585a08 Mup!MupClose+0x223
f79b39e4 80578c8c ff723ca0 00000000 00000000 nt!IopfCallDriver+0x31
f79b3a1c 805b0563 00723cb8 ff723ca0 00000000 nt!IopDeleteFile+0x132
f79b3a38 80522e47 ff723cb8 00000000 00000000 nt!ObpRemoveObjectRoutine+0xdf
f79b3a5c 80578470 8172ec70 814ef0ac f79b3c04 nt!ObfDereferenceObject+0x5f
f79b3b3c 805b465e 8172ec88 00000000 814ef008 nt!IopParseDevice+0xb0c
f79b3bc4 805b0b3f 00000000 f79b3c04 00000040 nt!ObpLookupObjectName+0x56a
f79b3c18 8056b133 00000000 00000000 00010001 nt!ObOpenObjectByName+0xeb
f79b3c94 8056baaa 02d3dbb0 00100080 02d3db50 nt!IopCreateFile+0x407
f79b3cf0 8056e17c 02d3dbb0 00100080 02d3db50 nt!IoCreateFile+0x8e
f79b3d30 8053d808 02d3dbb0 00100080 02d3db50 nt!NtCreateFile+0x30
f79b3d30 7c92eb94 02d3dbb0 00100080 02d3db50 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
02d3dba8 00000000 00000000 00000000 00000000 0x7c92eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
Mup!DfsBugCheck+2a
f96b729c 90 nop
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: Mup!DfsBugCheck+2a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Mup
IMAGE_NAME: Mup.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 41107ef8
FAILURE_BUCKET_ID: 0x82_Mup!DfsBugCheck+2a
BUCKET_ID: 0x82_Mup!DfsBugCheck+2a
And,notice that lines:
f79b3bc4 805b0b3f 00000000 f79b3c04 00000040 nt!ObpLookupObjectName+0x56a
kd> dt nt!_UNICODE_STRING 0xf79b3c04
“\Device\WinDfs\Root\192.168.1.108\test\test\1.txt”
+0x000 Length : 0x62
+0x002 MaximumLength : 0xf8
+0x004 Buffer : 0xe1133328 “\Device\WinDfs\Root\192.168.1.108\test\test\1.txt”
> In winxp sp1,sp2,it will crash.But in winxp sp3,everything is OK.
Then forget this. XP SP2 is obsolete. Just require SP3 in your product (at least when communicating with Samba).
–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com
I’m not sure I’d agree with the statement that in practice XP SP2 is obsolete, but as of next week,
xp gets pulled from mainstream support, so if msft sticks to that policy - it’s already been placed
on double secret probation several times - then it ain’t getting fixed, not that we didn’t know that
already for other reasons.
mm
Maxim S. Shatskih wrote:
> In winxp sp1,sp2,it will crash.But in winxp sp3,everything is OK.
Then forget this. XP SP2 is obsolete. Just require SP3 in your product (at least when communicating with Samba).
> I’m not sure I’d agree with the statement that in practice XP SP2 is obsolete
Yes, since SP3 is out.
, but as of next week, xp gets pulled from mainstream support
Wow. Interesting news.
–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com
Yes, but there is still a ton of XP SP2 out there.
It is indeed interesting news, though as XP has been placed on double secret probation several times
already, I guess we’ll have to see what happens, though I would say that they are serious this time.
http://www.pcauthority.com.au/News/142013,windows-xp-support-runs-out-next-week.aspx
mm
Maxim S. Shatskih wrote:
> I’m not sure I’d agree with the statement that in practice XP SP2 is obsolete
Yes, since SP3 is out.
> , but as of next week, xp gets pulled from mainstream support
Wow. Interesting news.