syzbot


possible deadlock in bch2_symlink

Status: upstream: reported C repro on 2024/09/29 07:31
Subsystems: bcachefs
[Documentation on labels]
Reported-by: syzbot+7836a68852a10ec3d790@syzkaller.appspotmail.com
First crash: 269d, last: 50d
Discussions (6)
Title Replies (including bot) Last reply
[syzbot] Monthly bcachefs report (Apr 2025) 0 (1) 2025/04/22 12:41
[syzbot] Monthly bcachefs report (Mar 2025) 0 (1) 2025/03/19 21:29
[syzbot] Monthly bcachefs report (Feb 2025) 0 (1) 2025/02/16 21:54
[syzbot] [bcachefs?] possible deadlock in bch2_symlink 0 (2) 2025/02/08 09:14
[syzbot] Monthly bcachefs report (Jan 2025) 0 (1) 2025/01/16 10:11
[syzbot] Monthly bcachefs report (Dec 2024) 0 (1) 2024/12/16 09:45
Last patch testing requests (1)
Created Duration User Patch Repo Result
2025/05/17 07:56 20m retest repro upstream OK log

Sample crash report:
bcachefs (loop3): reading snapshots table
bcachefs (loop3): reading snapshots done
bcachefs (loop3): done starting filesystem
============================================
WARNING: possible recursive locking detected
6.14.0-syzkaller-10892-g4e82c87058f4 #0 Not tainted
--------------------------------------------
syz.3.14/5986 is trying to acquire lock:
ffff88805a8abe08 (&sb->s_type->i_mutex_key#26){++++}-{4:4}, at: inode_lock include/linux/fs.h:867 [inline]
ffff88805a8abe08 (&sb->s_type->i_mutex_key#26){++++}-{4:4}, at: bch2_symlink+0x178/0x320 fs/bcachefs/fs.c:858

but task is already holding lock:
ffff88805a8ab670 (&sb->s_type->i_mutex_key#26){++++}-{4:4}, at: inode_lock include/linux/fs.h:867 [inline]
ffff88805a8ab670 (&sb->s_type->i_mutex_key#26){++++}-{4:4}, at: ovl_copy_up_workdir fs/overlayfs/copy_up.c:782 [inline]
ffff88805a8ab670 (&sb->s_type->i_mutex_key#26){++++}-{4:4}, at: ovl_do_copy_up fs/overlayfs/copy_up.c:1001 [inline]
ffff88805a8ab670 (&sb->s_type->i_mutex_key#26){++++}-{4:4}, at: ovl_copy_up_one fs/overlayfs/copy_up.c:1202 [inline]
ffff88805a8ab670 (&sb->s_type->i_mutex_key#26){++++}-{4:4}, at: ovl_copy_up_flags+0x19d7/0x47f0 fs/overlayfs/copy_up.c:1257

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

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

 *** DEADLOCK ***

 May be due to missing lock nesting notation

6 locks held by syz.3.14/5986:
 #0: ffff888025bd2420 (sb_writers#18){.+.+}-{0:0}, at: mnt_want_write+0x3f/0x90 fs/namespace.c:556
 #1: ffff888078339e50 (&ovl_i_mutex_dir_key[depth]/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:902 [inline]
 #1: ffff888078339e50 (&ovl_i_mutex_dir_key[depth]/1){+.+.}-{4:4}, at: do_unlinkat+0x26c/0x7b0 fs/namei.c:4595
 #2: ffff88807833a418 (&ovl_i_mutex_key[depth]){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:867 [inline]
 #2: ffff88807833a418 (&ovl_i_mutex_key[depth]){+.+.}-{4:4}, at: vfs_unlink+0xe4/0x650 fs/namei.c:4533
 #3: ffff88807833a7d0 (&ovl_i_lock_key[depth]){+.+.}-{4:4}, at: ovl_inode_lock_interruptible fs/overlayfs/overlayfs.h:651 [inline]
 #3: ffff88807833a7d0 (&ovl_i_lock_key[depth]){+.+.}-{4:4}, at: ovl_copy_up_start+0x53/0x310 fs/overlayfs/util.c:727
 #4: ffff888054182420 (sb_writers#17){.+.+}-{0:0}, at: ovl_copy_up_workdir fs/overlayfs/copy_up.c:781 [inline]
 #4: ffff888054182420 (sb_writers#17){.+.+}-{0:0}, at: ovl_do_copy_up fs/overlayfs/copy_up.c:1001 [inline]
 #4: ffff888054182420 (sb_writers#17){.+.+}-{0:0}, at: ovl_copy_up_one fs/overlayfs/copy_up.c:1202 [inline]
 #4: ffff888054182420 (sb_writers#17){.+.+}-{0:0}, at: ovl_copy_up_flags+0x19c0/0x47f0 fs/overlayfs/copy_up.c:1257
 #5: ffff88805a8ab670 (&sb->s_type->i_mutex_key#26){++++}-{4:4}, at: inode_lock include/linux/fs.h:867 [inline]
 #5: ffff88805a8ab670 (&sb->s_type->i_mutex_key#26){++++}-{4:4}, at: ovl_copy_up_workdir fs/overlayfs/copy_up.c:782 [inline]
 #5: ffff88805a8ab670 (&sb->s_type->i_mutex_key#26){++++}-{4:4}, at: ovl_do_copy_up fs/overlayfs/copy_up.c:1001 [inline]
 #5: ffff88805a8ab670 (&sb->s_type->i_mutex_key#26){++++}-{4:4}, at: ovl_copy_up_one fs/overlayfs/copy_up.c:1202 [inline]
 #5: ffff88805a8ab670 (&sb->s_type->i_mutex_key#26){++++}-{4:4}, at: ovl_copy_up_flags+0x19d7/0x47f0 fs/overlayfs/copy_up.c:1257

stack backtrace:
CPU: 1 UID: 0 PID: 5986 Comm: syz.3.14 Not tainted 6.14.0-syzkaller-10892-g4e82c87058f4 #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120
 print_deadlock_bug+0x2be/0x2d0 kernel/locking/lockdep.c:3042
 check_deadlock kernel/locking/lockdep.c:3094 [inline]
 validate_chain+0x928/0x24e0 kernel/locking/lockdep.c:3896
 __lock_acquire+0xad5/0xd80 kernel/locking/lockdep.c:5235
 lock_acquire+0x116/0x2f0 kernel/locking/lockdep.c:5866
 down_write+0x9c/0x220 kernel/locking/rwsem.c:1577
 inode_lock include/linux/fs.h:867 [inline]
 bch2_symlink+0x178/0x320 fs/bcachefs/fs.c:858
 vfs_symlink+0x137/0x2e0 fs/namei.c:4688
 ovl_do_symlink+0x85/0xd0 fs/overlayfs/overlayfs.h:268
 ovl_create_real+0x271/0x460 fs/overlayfs/dir.c:176
 ovl_copy_up_workdir fs/overlayfs/copy_up.c:783 [inline]
 ovl_do_copy_up fs/overlayfs/copy_up.c:1001 [inline]
 ovl_copy_up_one fs/overlayfs/copy_up.c:1202 [inline]
 ovl_copy_up_flags+0x1a0a/0x47f0 fs/overlayfs/copy_up.c:1257
 ovl_nlink_start+0x9c/0x410 fs/overlayfs/util.c:1165
 ovl_do_remove+0x242/0xda0 fs/overlayfs/dir.c:892
 vfs_unlink+0x365/0x650 fs/namei.c:4544
 do_unlinkat+0x442/0x7b0 fs/namei.c:4608
 __do_sys_unlink fs/namei.c:4654 [inline]
 __se_sys_unlink fs/namei.c:4652 [inline]
 __x64_sys_unlink+0x47/0x50 fs/namei.c:4652
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fc4ad18d169
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:00007fc4adf6f038 EFLAGS: 00000246 ORIG_RAX: 0000000000000057
RAX: ffffffffffffffda RBX: 00007fc4ad3a5fa0 RCX: 00007fc4ad18d169
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000200000000440
RBP: 00007fc4ad20e2a0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007fc4ad3a5fa0 R15: 00007ffc7a88c648
 </TASK>
bcachefs (loop3): shutting down
bcachefs (loop3): going read-only
bcachefs (loop3): finished waiting for writes to stop
bcachefs (loop3): flushing journal and stopping allocators, journal seq 5
bcachefs (loop3): flushing journal and stopping allocators complete, journal seq 5
bcachefs (loop3): clean shutdown complete, journal seq 6
bcachefs (loop3): marking filesystem clean
bcachefs (loop3): shutdown complete
syz.3.14 (5986) used greatest stack depth: 12208 bytes left

Crashes (1094):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/03/31 18:45 upstream 4e82c87058f4 d3999433 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in bch2_symlink
2025/05/02 20:12 upstream ebd297a2affa d7f099d1 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/05/02 15:10 upstream ebd297a2affa d7f099d1 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/05/02 00:10 upstream 4f79eaa2ceac 51b137cd .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/28 10:54 upstream b4432656b36e c6b4fb39 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/28 07:22 upstream b4432656b36e c6b4fb39 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/28 02:36 upstream b4432656b36e c6b4fb39 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/27 17:40 upstream 5bc1018675ec c6b4fb39 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/27 12:13 upstream 5bc1018675ec c6b4fb39 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/27 06:42 upstream 5bc1018675ec c6b4fb39 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/26 13:22 upstream f1a3944c860b c6b4fb39 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/24 03:11 upstream a79be02bba5c 9882047a .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/23 05:52 upstream bc3372351d0c 53a8b9bd .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/22 09:05 upstream a33b5a08cbbd 2a20f901 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/20 11:56 upstream 119009db2674 2a20f901 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/20 08:50 upstream 119009db2674 2a20f901 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/20 04:35 upstream 119009db2674 2a20f901 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/20 00:37 upstream 8560697b23dc 2a20f901 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/18 12:43 upstream fc96b232f8e7 2a20f901 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/18 07:27 upstream b5c6891b2c5b 2a20f901 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/18 07:27 upstream b5c6891b2c5b 2a20f901 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/17 22:55 upstream b5c6891b2c5b 2a20f901 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/17 18:27 upstream cfb2e2c57aef 552876f8 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/15 12:08 upstream 834a4a689699 85125322 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/15 06:50 upstream 834a4a689699 0bd6db41 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/15 02:03 upstream 834a4a689699 0bd6db41 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/14 10:55 upstream 8ffd015db85f 0bd6db41 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/14 00:31 upstream 5aaaedb0cb54 0bd6db41 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/13 23:02 upstream 5aaaedb0cb54 0bd6db41 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/13 20:43 upstream 5aaaedb0cb54 0bd6db41 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/13 14:50 upstream 7cdabafc0012 0bd6db41 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/13 08:20 upstream 7cdabafc0012 0bd6db41 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/12 17:03 upstream 3bde70a2c827 0bd6db41 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/12 01:58 upstream e618ee89561b 0bd6db41 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/11 07:04 upstream 0c7cae12f67c 94486846 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/09 19:47 upstream a24588245776 47d015b1 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/09 01:35 upstream bec7dcbc242c b133e63a .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/09 00:13 upstream bec7dcbc242c b133e63a .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/08 08:12 upstream 0af2f6be1b42 a2ada0e7 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/07 07:54 upstream 0af2f6be1b42 1c65791e .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/06 20:20 upstream f4d2ef48250a 1c65791e .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/06 19:17 upstream f4d2ef48250a 1c65791e .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/06 19:17 upstream f4d2ef48250a 1c65791e .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/05 09:49 upstream a8662bcd2ff1 1c65791e .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/04/04 09:12 upstream 06a22366d6a1 1740c707 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2025/02/08 09:14 upstream 7ee983c850b4 ef44b750 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2024/09/28 18:11 upstream ad46e8f95e93 ba29ff75 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2024/09/25 07:23 upstream 68e5c7d4cefb 349a68c4 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in bch2_symlink
2024/12/31 06:20 linux-next 8155b4ef3466 d3ccff63 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in bch2_symlink
* Struck through repros no longer work on HEAD.