ci2 starts bisection 2022-11-07 06:28:21.38230683 +0000 UTC m=+293842.738734741 bisecting fixing commit since 833477fce7a14d43ae4c07f8ddc32fa5119471a2 building syzkaller on 80b58a4201a50d022574c185b387d54b3d442aae ensuring issue is reproducible on original commit 833477fce7a14d43ae4c07f8ddc32fa5119471a2 testing commit 833477fce7a14d43ae4c07f8ddc32fa5119471a2 gcc compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: c2dc40f196ef7a729a63bc3659f2955fd1685b2f34cc30a43660260b67e2d5a0 run #0: crashed: possible deadlock in path_openat run #1: crashed: possible deadlock in path_openat run #2: crashed: possible deadlock in mnt_want_write_file run #3: crashed: possible deadlock in mnt_want_write_file run #4: crashed: possible deadlock in path_openat run #5: crashed: possible deadlock in mnt_want_write_file run #6: crashed: possible deadlock in mnt_want_write_file run #7: crashed: possible deadlock in mnt_want_write_file run #8: crashed: possible deadlock in mnt_want_write_file run #9: crashed: possible deadlock in path_openat run #10: crashed: possible deadlock in mnt_want_write_file run #11: crashed: possible deadlock in mnt_want_write_file run #12: crashed: possible deadlock in mnt_want_write_file run #13: crashed: possible deadlock in mnt_want_write_file run #14: crashed: possible deadlock in mnt_want_write_file run #15: crashed: possible deadlock in mnt_want_write_file run #16: crashed: possible deadlock in mnt_want_write_file run #17: crashed: possible deadlock in mnt_want_write_file run #18: crashed: possible deadlock in path_openat run #19: crashed: possible deadlock in mnt_want_write_file testing current HEAD f0c4d9fc9cc9462659728d168387191387e903cc testing commit f0c4d9fc9cc9462659728d168387191387e903cc gcc compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: af3460c7f6653520a2a4e6b0b01c452e2398be99ef3df92da7449b8becb51d4b run #0: crashed: possible deadlock in mnt_want_write_file run #1: crashed: possible deadlock in path_openat run #2: crashed: possible deadlock in mnt_want_write_file run #3: crashed: possible deadlock in mnt_want_write_file run #4: crashed: possible deadlock in mnt_want_write_file run #5: crashed: possible deadlock in mnt_want_write_file run #6: crashed: possible deadlock in path_openat run #7: crashed: possible deadlock in mnt_want_write_file run #8: crashed: possible deadlock in mnt_want_write_file run #9: crashed: possible deadlock in mnt_want_write_file revisions tested: 2, total time: 34m31.109249842s (build: 26m24.388144404s, test: 7m34.26828429s) the crash still happens on HEAD commit msg: Linux 6.1-rc4 crash: possible deadlock in mnt_want_write_file REISERFS (device loop0): checking transaction log (loop0) REISERFS (device loop0): Using rupasov hash to sort names REISERFS (device loop0): Created .reiserfs_priv - reserved for xattr storage. ====================================================== WARNING: possible circular locking dependency detected 6.1.0-rc4-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.0/4177 is trying to acquire lock: ffff88807d02e460 (sb_writers#13){.+.+}-{0:0}, at: mnt_want_write_file+0x57/0x190 fs/namespace.c:437 but task is already holding lock: ffff88807cc80090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x6d/0xc0 fs/reiserfs/lock.c:27 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&sbi->lock){+.+.}-{3:3}: lock_acquire+0x182/0x3c0 kernel/locking/lockdep.c:5668 __mutex_lock_common+0x1bd/0x26e0 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799 reiserfs_write_lock+0x6d/0xc0 fs/reiserfs/lock.c:27 reiserfs_lookup+0x11b/0x3c0 fs/reiserfs/namei.c:364 __lookup_slow+0x212/0x2f0 fs/namei.c:1685 lookup_one_len+0x4b4/0x4f0 fs/namei.c:2711 reiserfs_lookup_privroot+0x81/0x1d0 fs/reiserfs/xattr.c:973 reiserfs_fill_super+0x1bd0/0x20d0 fs/reiserfs/super.c:2174 mount_bdev+0x27a/0x370 fs/super.c:1401 legacy_get_tree+0xe4/0x170 fs/fs_context.c:610 vfs_get_tree+0x7b/0x220 fs/super.c:1531 do_new_mount+0x1df/0x930 fs/namespace.c:3040 do_mount fs/namespace.c:3383 [inline] __do_sys_mount fs/namespace.c:3591 [inline] __se_sys_mount+0x20f/0x2a0 fs/namespace.c:3568 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #1 (&type->i_mutex_dir_key#8){+.+.}-{3:3}: lock_acquire+0x182/0x3c0 kernel/locking/lockdep.c:5668 down_write+0x9c/0x270 kernel/locking/rwsem.c:1562 inode_lock include/linux/fs.h:756 [inline] open_last_lookups fs/namei.c:3478 [inline] path_openat+0x6e1/0x27e0 fs/namei.c:3710 do_filp_open+0x256/0x4a0 fs/namei.c:3740 do_sys_openat2+0xfc/0x410 fs/open.c:1310 do_sys_open fs/open.c:1326 [inline] __do_sys_creat fs/open.c:1402 [inline] __se_sys_creat fs/open.c:1396 [inline] __x64_sys_creat+0x11a/0x160 fs/open.c:1396 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #0 (sb_writers#13){.+.+}-{0:0}: check_prev_add kernel/locking/lockdep.c:3097 [inline] check_prevs_add kernel/locking/lockdep.c:3216 [inline] validate_chain+0x1898/0x6ae0 kernel/locking/lockdep.c:3831 __lock_acquire+0x1292/0x1f60 kernel/locking/lockdep.c:5055 lock_acquire+0x182/0x3c0 kernel/locking/lockdep.c:5668 percpu_down_read include/linux/percpu-rwsem.h:51 [inline] __sb_start_write include/linux/fs.h:1826 [inline] sb_start_write+0x47/0x130 include/linux/fs.h:1901 mnt_want_write_file+0x57/0x190 fs/namespace.c:437 reiserfs_ioctl+0x143/0x2b0 fs/reiserfs/ioctl.c:103 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:870 [inline] __se_sys_ioctl+0xa7/0xf0 fs/ioctl.c:856 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd other info that might help us debug this: Chain exists of: sb_writers#13 --> &type->i_mutex_dir_key#8 --> &sbi->lock Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&sbi->lock); lock(&type->i_mutex_dir_key#8); lock(&sbi->lock); lock(sb_writers#13); *** DEADLOCK *** 1 lock held by syz-executor.0/4177: #0: ffff88807cc80090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x6d/0xc0 fs/reiserfs/lock.c:27 stack backtrace: CPU: 1 PID: 4177 Comm: syz-executor.0 Not tainted 6.1.0-rc4-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x12a/0x1be lib/dump_stack.c:106 check_noncircular+0x2cc/0x390 kernel/locking/lockdep.c:2177 check_prev_add kernel/locking/lockdep.c:3097 [inline] check_prevs_add kernel/locking/lockdep.c:3216 [inline] validate_chain+0x1898/0x6ae0 kernel/locking/lockdep.c:3831 __lock_acquire+0x1292/0x1f60 kernel/locking/lockdep.c:5055 lock_acquire+0x182/0x3c0 kernel/locking/lockdep.c:5668 percpu_down_read include/linux/percpu-rwsem.h:51 [inline] __sb_start_write include/linux/fs.h:1826 [inline] sb_start_write+0x47/0x130 include/linux/fs.h:1901 mnt_want_write_file+0x57/0x190 fs/namespace.c:437 reiserfs_ioctl+0x143/0x2b0 fs/reiserfs/ioctl.c:103 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:870 [inline] __se_sys_ioctl+0xa7/0xf0 fs/ioctl.c:856 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7fc6cb48a5a9 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 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fc6cc515168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007fc6cb5abf80 RCX: 00007fc6cb48a5a9 RDX: 0000000000000000 RSI: 0000000040087602 RDI: 0000000000000005 RBP: 00007fc6cb4e5580 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffdfde7df7f R14: 00007fc6cc515300 R15: 0000000000022000