syzbot


possible deadlock in __simple_recursive_removal

Status: upstream: reported C repro on 2025/07/02 18:04
Subsystems: fs
[Documentation on labels]
Reported-by: syzbot+6d7771315ecb9233f395@syzkaller.appspotmail.com
First crash: 38d, last: 36d
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [fs?] possible deadlock in __simple_recursive_removal 1 (5) 2025/07/03 09:24
Last patch testing requests (4)
Created Duration User Patch Repo Result
2025/07/17 23:22 24m retest repro linux-next OK log
2025/07/03 09:24 0m lizhi.xu@windriver.com patch linux-next error
2025/07/03 09:21 1h21m lizhi.xu@windriver.com patch linux-next OK log
2025/07/03 02:49 25m lizhi.xu@windriver.com patch linux-next OK log

Sample crash report:
============================================
WARNING: possible recursive locking detected
6.16.0-rc4-next-20250702-syzkaller #0 Not tainted
--------------------------------------------
syz.4.1669/11445 is trying to acquire lock:
ffff888074570148 (&sb->s_type->i_mutex_key#17){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:869 [inline]
ffff888074570148 (&sb->s_type->i_mutex_key#17){+.+.}-{4:4}, at: __simple_recursive_removal+0x95/0x510 fs/libfs.c:614

but task is already holding lock:
ffff88802326a988 (&sb->s_type->i_mutex_key#17){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:869 [inline]
ffff88802326a988 (&sb->s_type->i_mutex_key#17){+.+.}-{4:4}, at: bm_entry_write+0x289/0x540 fs/binfmt_misc.c:737

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

       CPU0
       ----
  lock(&sb->s_type->i_mutex_key#17);
  lock(&sb->s_type->i_mutex_key#17);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

3 locks held by syz.4.1669/11445:
 #0: ffff888034c7a7f8 (&f->f_pos_lock){+.+.}-{4:4}, at: fdget_pos+0x247/0x320 fs/file.c:1232
 #1: ffff8880238a2428 (sb_writers#11){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3098 [inline]
 #1: ffff8880238a2428 (sb_writers#11){.+.+}-{0:0}, at: vfs_write+0x211/0xa90 fs/read_write.c:682
 #2: ffff88802326a988 (&sb->s_type->i_mutex_key#17){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:869 [inline]
 #2: ffff88802326a988 (&sb->s_type->i_mutex_key#17){+.+.}-{4:4}, at: bm_entry_write+0x289/0x540 fs/binfmt_misc.c:737

stack backtrace:
CPU: 0 UID: 0 PID: 11445 Comm: syz.4.1669 Not tainted 6.16.0-rc4-next-20250702-syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
 print_deadlock_bug+0x28b/0x2a0 kernel/locking/lockdep.c:3044
 check_deadlock kernel/locking/lockdep.c:3096 [inline]
 validate_chain+0x1a3f/0x2140 kernel/locking/lockdep.c:3898
 __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5240
 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5871
 down_write+0x96/0x1f0 kernel/locking/rwsem.c:1577
 inode_lock include/linux/fs.h:869 [inline]
 __simple_recursive_removal+0x95/0x510 fs/libfs.c:614
 remove_binfmt_handler fs/binfmt_misc.c:694 [inline]
 bm_entry_write+0x4f7/0x540 fs/binfmt_misc.c:749
 vfs_write+0x27e/0xa90 fs/read_write.c:684
 ksys_write+0x145/0x250 fs/read_write.c:738
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7ff7d318e929
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ff7d0fd5038 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007ff7d33b6160 RCX: 00007ff7d318e929
RDX: 0000000000000002 RSI: 0000200000000100 RDI: 0000000000000009
RBP: 00007ff7d3210b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007ff7d33b6160 R15: 00007ffcfd412bd8
 </TASK>

Crashes (38):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/07/03 23:19 linux-next 50c8770a42fa 115ceea7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in __simple_recursive_removal
2025/07/03 23:19 linux-next 50c8770a42fa 115ceea7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in __simple_recursive_removal
2025/07/03 22:03 linux-next 50c8770a42fa 115ceea7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in __simple_recursive_removal
2025/07/03 22:02 linux-next 50c8770a42fa 115ceea7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in __simple_recursive_removal
2025/07/03 00:53 linux-next 50c8770a42fa 0cd59a8f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in __simple_recursive_removal
2025/07/03 00:53 linux-next 50c8770a42fa 0cd59a8f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in __simple_recursive_removal
2025/07/02 23:26 linux-next 50c8770a42fa 0cd59a8f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in __simple_recursive_removal
2025/07/02 23:25 linux-next 50c8770a42fa 0cd59a8f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in __simple_recursive_removal
2025/07/02 20:18 linux-next 50c8770a42fa 0cd59a8f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in __simple_recursive_removal
2025/07/02 20:18 linux-next 50c8770a42fa 0cd59a8f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in __simple_recursive_removal
2025/07/02 18:20 linux-next 50c8770a42fa 0cd59a8f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in __simple_recursive_removal
2025/07/02 18:17 linux-next 50c8770a42fa 0cd59a8f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in __simple_recursive_removal
2025/07/02 16:50 linux-next 50c8770a42fa 0cd59a8f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in __simple_recursive_removal
2025/07/02 16:44 linux-next 50c8770a42fa 0cd59a8f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in __simple_recursive_removal
2025/07/02 16:32 linux-next 50c8770a42fa 0cd59a8f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in __simple_recursive_removal
2025/07/02 16:28 linux-next 50c8770a42fa 0cd59a8f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in __simple_recursive_removal
2025/07/02 16:00 linux-next 50c8770a42fa 0cd59a8f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in __simple_recursive_removal
2025/07/02 15:46 linux-next 50c8770a42fa 0cd59a8f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in __simple_recursive_removal
2025/07/02 15:45 linux-next 50c8770a42fa 0cd59a8f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in __simple_recursive_removal
2025/07/02 15:14 linux-next 50c8770a42fa 0cd59a8f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in __simple_recursive_removal
2025/07/02 15:14 linux-next 50c8770a42fa 0cd59a8f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in __simple_recursive_removal
2025/07/02 15:14 linux-next 50c8770a42fa 0cd59a8f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in __simple_recursive_removal
2025/07/02 14:50 linux-next 50c8770a42fa 0cd59a8f .config strace log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in __simple_recursive_removal
2025/07/02 13:37 linux-next 50c8770a42fa 0cd59a8f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in __simple_recursive_removal
2025/07/02 13:36 linux-next 50c8770a42fa 0cd59a8f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in __simple_recursive_removal
2025/07/02 13:23 linux-next 50c8770a42fa 0cd59a8f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in __simple_recursive_removal
2025/07/02 13:21 linux-next 50c8770a42fa 0cd59a8f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in __simple_recursive_removal
2025/07/02 13:21 linux-next 50c8770a42fa 0cd59a8f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in __simple_recursive_removal
2025/07/02 12:46 linux-next 50c8770a42fa 0cd59a8f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in __simple_recursive_removal
2025/07/02 12:46 linux-next 50c8770a42fa 0cd59a8f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in __simple_recursive_removal
2025/07/02 12:15 linux-next 50c8770a42fa ffe4b334 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in __simple_recursive_removal
2025/07/02 12:13 linux-next 50c8770a42fa ffe4b334 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in __simple_recursive_removal
2025/07/02 12:06 linux-next 50c8770a42fa ffe4b334 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in __simple_recursive_removal
2025/07/02 12:03 linux-next 50c8770a42fa ffe4b334 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in __simple_recursive_removal
2025/07/02 11:49 linux-next 50c8770a42fa ffe4b334 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in __simple_recursive_removal
2025/07/02 11:49 linux-next 50c8770a42fa ffe4b334 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in __simple_recursive_removal
2025/07/02 11:21 linux-next 50c8770a42fa ffe4b334 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in __simple_recursive_removal
2025/07/02 11:21 linux-next 50c8770a42fa ffe4b334 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in __simple_recursive_removal
* Struck through repros no longer work on HEAD.