possible deadlock in mnt_want_write (9)

Status: upstream: reported C repro on 2026/08/05 08:12
Subsystems: fs usb
Labels: prio:low
[Documentation on labels]
Reported-by: syzbot+da381387152f0dd8bedf@syzkaller.appspotmail.com
First crash: 101d, last: 4d20h
Cause bisection: introduced by (bisect log) [merge commit]:
commit af96134dc8562f9fcbb8358af36f6086619a29ab
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Tue Jun 27 17:37:01 2023 +0000

  Merge tag 'rcu.2023.06.22a' of git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu

Crash: possible deadlock in mnt_want_write (log)
Repro: C syz .config
  
▶ ▼ ✨ AI Patch Versions (1)
Version Stage Reported Report Link Job
1 moderation 2026/08/05 12:22 Discussion 43881a07-9f58-4a9b-b110-6696a48ed088
▶ ▼ ✨ AI Jobs (2)
ID Workflow Result Correct Bug Created Started Finished Revision
43881a07 patching ❓ possible deadlock in mnt_want_write (9) 2026/08/05 08:19 2026/08/05 08:19 2026/08/05 12:22 52aa2820
13c50770 assessment-security DenialOfService: ✅ Exploitable: ❌ FilesystemTrigger: ❌ NetworkTrigger: ❌ PeripheralTrigger: ❌ RemoteTrigger: ❌ Unprivileged: ❌ UserNamespace: ❌ VMGuestTrigger: ❌ VMHostTrigger: ❌ ❓ possible deadlock in mnt_want_write (9) 2026/08/03 00:23 2026/08/03 00:23 2026/08/03 01:12 e611ffe1
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [overlayfs?] possible deadlock in mnt_want_write (9) 0 (1) 2026/08/05 08:12
▶ ▼ Similar bugs (15)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in mnt_want_write (8) ext4 4 syz, C 3 137d 154d 0/29 closed as dup on 2026/06/09 14:03
linux-6.6 possible deadlock in mnt_want_write 4 10 39d 101d 0/2 upstream: reported on 2026/08/01 11:19
linux-5.15 possible deadlock in mnt_want_write missing-backport 4 syz, C done 117 1078d 1330d 0/3 auto-obsoleted due to no activity on 2024/10/15 12:27
upstream possible deadlock in mnt_want_write (6) kernfs 4 1 518d 514d 0/29 auto-obsoleted due to no activity on 2025/08/08 23:21
upstream possible deadlock in mnt_want_write fs 4 syz, C done done 662 2224d 3031d 15/29 fixed on 2020/11/16 12:12
upstream possible deadlock in mnt_want_write (5) kernfs 4 1 668d 664d 0/29 auto-obsoleted due to no activity on 2025/04/20 18:48
linux-5.15 possible deadlock in mnt_want_write (2) 4 4 91d 98d 0/3 upstream: reported on 2026/08/04 15:47
linux-6.1 possible deadlock in mnt_want_write origin:upstream missing-backport 4 syz, C done 61 36d 1323d 0/3 upstream: reported C repro on 2023/03/28 13:05
linux-4.19 possible deadlock in mnt_want_write romfs 4 syz, C 730 1344d 2761d 0/1 upstream: reported C repro on 2019/04/19 16:54
android-49 possible deadlock in mnt_want_write 4 1 3014d 3014d 0/3 auto-closed as invalid on 2019/02/22 14:57
upstream possible deadlock in mnt_want_write (4) kernfs 4 1 794d 790d 0/29 auto-obsoleted due to no activity on 2024/12/16 14:12
upstream possible deadlock in mnt_want_write (2) integrity overlayfs 4 syz, C done 867 1105d 1973d 25/29 fixed on 2023/12/21 01:43
upstream possible deadlock in mnt_want_write (3) kernfs 4 9 941d 1044d 0/29 auto-obsoleted due to no activity on 2024/07/22 10:45
upstream possible deadlock in mnt_want_write (7) fs 4 3 313d 316d 0/29 auto-obsoleted due to no activity on 2026/04/11 06:22
linux-4.14 possible deadlock in mnt_want_write ubifs 4 syz, C 10467 1344d 2756d 0/1 upstream: reported C repro on 2019/04/25 05:09

Sample crash report:
LUN: removable file: (no medium)
============================================
WARNING: possible recursive locking detected
syzkaller #0 Not tainted
--------------------------------------------
syz-executor348/5606 is trying to acquire lock:
ffff88801d7d8510 (sb_writers#8){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:494

but task is already holding lock:
ffff88801d7d8510 (sb_writers#8){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2753 [inline]
ffff88801d7d8510 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x231/0xbb0 fs/read_write.c:683

other info that might help us debug this:
 Possible unsafe locking scenario:

       CPU0
       ----
  lock(sb_writers#8);
  lock(sb_writers#8);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

locks held by syz-executor348/5606: 4, last CPU#0:
 #0: ffff88801d7d8510 (sb_writers#8){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2753 [inline]
 #0: ffff88801d7d8510 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x231/0xbb0 fs/read_write.c:683
 #1: ffff8880284d5078 (&buffer->mutex){+.+.}-{4:4}, at: configfs_write_iter+0x81/0x430 fs/configfs/file.c:226
 #2: ffff888033121d68 (&p->frag_sem){.+.+}-{4:4}, at: flush_write_buffer fs/configfs/file.c:205 [inline]
 #2: ffff888033121d68 (&p->frag_sem){.+.+}-{4:4}, at: configfs_write_iter+0x23b/0x430 fs/configfs/file.c:229
 #3: ffff888035be4198 (&common->filesem){+.+.}-{4:4}, at: fsg_store_file+0x163/0x400 drivers/usb/gadget/function/storage_common.c:452

stack backtrace:
CPU: 0 UID: 0 PID: 5606 Comm: syz-executor348 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/16/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 print_deadlock_bug+0x27a/0x290 kernel/locking/lockdep.c:3085
 check_deadlock kernel/locking/lockdep.c:3137 [inline]
 validate_chain kernel/locking/lockdep.c:3939 [inline]
 __lock_acquire+0x25db/0x2de0 kernel/locking/lockdep.c:5288
 lock_acquire+0x115/0x350 kernel/locking/lockdep.c:5942
 percpu_down_read_internal include/linux/percpu-rwsem.h:53 [inline]
 percpu_down_read_freezable include/linux/percpu-rwsem.h:83 [inline]
 __sb_start_write include/linux/fs/super.h:19 [inline]
 sb_start_write+0x4d/0x1d0 include/linux/fs/super.h:125
 mnt_want_write+0x41/0x90 fs/namespace.c:494
 lookup_open+0x1ec/0x1a60 fs/namei.c:4451
 open_last_lookups fs/namei.c:4767 [inline]
 path_openat+0x67c/0x1d60 fs/namei.c:4997
 do_file_open+0x23e/0x4a0 fs/namei.c:5029
 file_open_name fs/open.c:1375 [inline]
 filp_open+0x16d/0x1d0 fs/open.c:1392
 fsg_lun_open+0x6c/0xe00 drivers/usb/gadget/function/storage_common.c:194
 fsg_store_file+0x19e/0x400 drivers/usb/gadget/function/storage_common.c:455
 flush_write_buffer fs/configfs/file.c:207 [inline]
 configfs_write_iter+0x33a/0x430 fs/configfs/file.c:229
 new_sync_write fs/read_write.c:595 [inline]
 vfs_write+0x61e/0xbb0 fs/read_write.c:687
 ksys_write+0x156/0x270 fs/read_write.c:739
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f0781989649
Code: c0 79 93 eb d5 48 8d 7c 1d 00 eb 99 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 d8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffc9bb511f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 6769666e6f632f2e RCX: 00007f0781989649
RDX: 0000000000000005 RSI: 00002000000003c0 RDI: 0000000000000003
RBP: 0000000000000001 R08: 0000000000000006 R09: 0000000000000006
R10: 0000000000000006 R11: 0000000000000246 R12: 00007ffc9bb51368
R13: 431bde82d7b634db R14: 00007f0781a1cc40 R15: 0000000000000002
 </TASK>
mass_storage.0/lun.0: unable to open backing file: file0

Crashes (214):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/10/04 05:26 upstream a74306e2e676 57bbd979 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mnt_want_write
2026/08/02 10:51 linux-next cc2b5f627e8c e611ffe1 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/09/10 11:05 upstream 50d05c7c76c9 4e8b1cc6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in mnt_want_write
2026/09/03 08:00 upstream 940de590b839 6a988719 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in mnt_want_write
2026/11/02 07:12 upstream 46fec1c3029b 25a0ae84 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mnt_want_write
2026/10/31 16:58 upstream 36aad21d50d1 2041d3f8 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mnt_want_write
2026/10/01 04:24 upstream 551c722f4080 4db88980 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mnt_want_write
2026/11/05 19:36 linux-next ddfe51b0a0f5 5cecaf1f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in mnt_want_write
2026/10/25 13:33 linux-next 20a33c6b6cbe 1d9ca40b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in mnt_want_write
2026/10/21 12:20 linux-next 8f7df005a756 61c200c7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/10/20 10:31 linux-next 3d229ce89862 72cdc28d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in mnt_want_write
2026/10/19 05:23 linux-next 2efb7a11f1aa 432c0077 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/10/16 11:58 linux-next b810335a0699 b1757810 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/10/16 08:36 linux-next b810335a0699 3f2522c6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/10/15 21:37 linux-next b810335a0699 3f2522c6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in mnt_want_write
2026/10/15 12:22 linux-next d419d682257d 8fb0ae89 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/10/15 10:53 linux-next d419d682257d 8fb0ae89 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/10/15 04:36 linux-next d419d682257d 8fb0ae89 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/10/15 01:23 linux-next d419d682257d 8fb0ae89 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in mnt_want_write
2026/10/14 22:16 linux-next d419d682257d 8fb0ae89 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/10/14 19:25 linux-next d419d682257d 7321cd29 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in mnt_want_write
2026/10/14 04:09 linux-next 1fffefb00cc0 7321cd29 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in mnt_want_write
2026/10/14 02:16 linux-next 1fffefb00cc0 7321cd29 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in mnt_want_write
2026/10/14 00:38 linux-next 1fffefb00cc0 7321cd29 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/10/13 14:05 linux-next 4eb2586bd40d 7321cd29 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/10/12 17:06 linux-next becb95e45ef0 745a967f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in mnt_want_write
2026/10/12 15:30 linux-next becb95e45ef0 745a967f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in mnt_want_write
2026/10/12 08:47 linux-next becb95e45ef0 4f92358f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/10/12 00:13 linux-next becb95e45ef0 4f92358f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/10/11 18:33 linux-next becb95e45ef0 4f92358f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/10/11 14:09 linux-next becb95e45ef0 4f92358f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in mnt_want_write
2026/10/10 21:06 linux-next becb95e45ef0 4f92358f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/10/10 07:43 linux-next becb95e45ef0 4f92358f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/10/09 12:46 linux-next aac26bee2287 a8add9cd .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/10/09 09:47 linux-next aac26bee2287 b2734a59 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/10/09 07:01 linux-next aac26bee2287 b2734a59 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/10/09 00:28 linux-next b01868671970 b2734a59 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/10/08 23:26 linux-next b01868671970 b2734a59 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/10/08 19:09 linux-next b01868671970 4f6a9fcf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/10/08 17:24 linux-next b01868671970 4f6a9fcf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/10/08 16:00 linux-next b01868671970 4f6a9fcf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/10/08 15:01 linux-next b01868671970 4f6a9fcf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/10/08 13:06 linux-next b01868671970 4f6a9fcf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/10/08 05:54 linux-next b01868671970 6520ecdb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/10/07 18:59 linux-next b01868671970 6520ecdb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in mnt_want_write
2026/10/07 14:42 linux-next eea3fef32a9c 6520ecdb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in mnt_want_write
2026/10/07 10:17 linux-next eea3fef32a9c f7710056 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/10/07 08:35 linux-next eea3fef32a9c f7710056 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/10/07 02:53 linux-next eea3fef32a9c f7710056 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/10/06 22:38 linux-next eea3fef32a9c f7710056 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/10/06 11:33 linux-next bf1ee2bd5c2d f7710056 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/10/06 03:31 linux-next bf1ee2bd5c2d f7710056 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in mnt_want_write
2026/10/05 20:01 linux-next bf1ee2bd5c2d 1995e6c7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in mnt_want_write
2026/10/05 19:54 linux-next bf1ee2bd5c2d 1995e6c7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in mnt_want_write
2026/10/05 13:02 linux-next f0406245cb98 1995e6c7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in mnt_want_write
2026/09/25 16:48 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci e8e60d3ddd25 f281d9d2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in mnt_want_write
* Struck through repros no longer work on HEAD.