Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows 11 BSOD when the drive is accessed over the network (Samba) #678

Open
TimedPing opened this issue Jul 18, 2024 · 6 comments
Open

Comments

@TimedPing
Copy link

Windows 11 23H2 system crashed (BSOD) when the drive is shared via windows Samba (Network Share) and accessed by other device via the network.
This problem happened even with latest version (as of writing, 1.9) BTRFS driver and clean installation of windows, across multiple non-identical system.

How to replicate the problem:
-Make the BTRFS drive as shared drive in Windows disk properties
-Access the assigned drive on other devices (other windows/linux PC and Mac, Android device, etc)
-Try to access any file on the drive.
-The system crashed as soon as file being accessed, usually throwing Memory Management BSOD

@maharmstone
Copy link
Owner

Can you send a minidump?

@TimedPing
Copy link
Author

Can you send a minidump?

Sure thing!
071824-7578-01.dmp

@maharmstone
Copy link
Owner

maharmstone commented Jul 20, 2024

Thanks. This is called from within the call to CcMdlRead at https://github.com/maharmstone/btrfs/blob/master/src/read.c#L3379...

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000103087, The subtype of the BugCheck.
Arg2: ffffb0081dd0b290
Arg3: 0000000000000000
Arg4: 0000000000000000

00 ffffe488`22d62788 fffff805`686ce1eb     : 00000000`0000001a 00000000`00103087 ffffb008`1dd0b290 00000000`00000000 : nt!KeBugCheckEx
01 ffffe488`22d62790 fffff805`684e4e5d     : 00000000`00000000 ffffb008`06dd9038 ffffb008`06dd9038 00000000`00000000 : nt!MmMapViewInSystemCache+0x1e9dfb
02 ffffe488`22d62820 fffff805`6851ee55     : 00000000`00000000 00000000`00040000 ffffb008`00000000 00000000`00000000 : nt!CcGetVacbMiss+0x1ed
03 ffffe488`22d628b0 fffff805`689a6116     : 00000000`00000000 00000000`00000000 ffffe488`22d629a8 ffffe488`22d62998 : nt!CcGetVirtualAddress+0x235
04 ffffe488`22d62940 fffff805`822c2603     : ffffb008`1dc7db10 ffffb008`160bfeb0 00000000`000c0000 ffffb008`160bfa28 : nt!CcMdlRead+0xc6
05 ffffe488`22d62a30 fffff805`822c2b8c     : ffffb008`0d4a4030 00000000`00000000 ffffd20c`255bc7c0 ffffb008`0d4a4001 : btrfs!do_read+0x143 [z:\workspace\maharmstone\btrfs\0d913aca\src\read.c @ 3379] 
06 ffffe488`22d62b00 fffff805`684c1ab5     : ffffe488`00000000 00000000`00000000 ffffb008`144eda00 ffffb008`160bfee0 : btrfs!drv_read+0x1fc [z:\workspace\maharmstone\btrfs\0d913aca\src\read.c @ 3609] 
07 ffffe488`22d62b70 fffff805`6774a1fb     : 00000000`00000000 ffffb008`14f26040 00000000`00000006 fffff805`684201b3 : nt!IofCallDriver+0x55
08 ffffe488`22d62bb0 fffff805`67747e43     : ffffe488`22d62c40 00000000`00000000 ffffb008`144eda00 ffffb008`1dc7db10 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x15b
09 ffffe488`22d62c20 fffff805`684c1ab5     : ffffb008`1cecca90 00000000`00000026 00000000`00000000 00000000`00000000 : FLTMGR!FltpDispatch+0xa3
0a ffffe488`22d62c80 fffff805`65e58766     : ffffb008`1cecca90 00000000`00000000 ffffb008`1cecc760 00000000`00000000 : nt!IofCallDriver+0x55
0b ffffe488`22d62cc0 fffff805`65e638c6     : 00000000`0000000c ffffb008`1cecc760 fffff805`65e40048 ffffe488`22d62e2c : srv2!Smb2ExecuteRead+0x1e6
0c ffffe488`22d62d60 fffff805`65e58b29     : ffffb008`16b85cd0 ffffb008`16b85be0 fffff805`65e40048 ffffb008`16b85cd0 : srv2!Smb2ExecuteProviderCallback+0x76
0d ffffe488`22d62dc0 fffff805`65e58a56     : ffffb008`1cecc760 00000000`00000000 00000000`00000000 fffff805`65e0227f : srv2!Srv2CallProviders+0x99
0e ffffe488`22d62e00 fffff805`65e187c2     : ffffb008`1cecc760 ffffb008`1cecc760 ffffb008`169ffe00 00000000`00000026 : srv2!Srv2ProcessPacket+0xa6
0f ffffe488`22d62e50 fffff805`65e74eed     : ffffb008`1cecc760 ffffb008`169ffe40 ffffb008`169ffe50 ffffe488`22d38901 : srv2!Srv2PlainTextReceiveHandler+0x172
10 ffffe488`22d62e90 fffff805`65e62f2e     : ffff9900`00000000 ffffb008`1cecc780 ffffb008`169ffe50 ffffb008`0d50f340 : srv2!Srv2DecryptMessageAsync+0xdd
11 ffffe488`22d62ed0 fffff805`6861ab1e     : ffffe488`22d62f00 ffffe488`22d60190 3ee8b7ee`3ee7b12e ffffffff`ee1e5d00 : srv2!RfspThreadPoolNodeWorkerProcessWorkItems+0x17e
12 ffffe488`22d62f60 fffff805`6861aadc     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxSwitchKernelStackCallout+0x2e (TrapFrame @ ffffe488`22d62e20)
13 ffffe488`22d38960 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue

Possibly something related at winfsp/winfsp#217

@maharmstone
Copy link
Owner

So it's not documented what exactly 103087 means, but it looks like maybe it's something to do with not being aligned to a page size. Can you remember what program you were using on the other end when the crash happened?

@TimedPing
Copy link
Author

So it's not documented what exactly 103087 means, but it looks like maybe it's something to do with not being aligned to a page size. Can you remember what program you were using on the other end when the crash happened?

well, other side either accessing via Thunar/Dolphin (Linux), Windows Explorer, or FX explorer on android, all of it causing crashes (BSOD), even with file as small as 1KB text document.

@maharmstone
Copy link
Owner

I can't reproduce it in Windows 11 23H2 22631.2428.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants