reiserfs: enabling write barrier flush mode REISERFS (device loop0): Created .reiserfs_priv - reserved for xattr storage. ====================================================== WARNING: possible circular locking dependency detected 6.7.0-syzkaller-g0dd3ee311255 #0 Not tainted ------------------------------------------------------ syz-executor.0/5488 is trying to acquire lock: ffff888029999090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x79/0x100 fs/reiserfs/lock.c:27 but task is already holding lock: ffff8880684d29c0 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:837 [inline] ffff8880684d29c0 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: do_unlinkat+0x284/0x740 fs/namei.c:4369 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}: down_write_nested+0x3d/0x50 kernel/locking/rwsem.c:1695 inode_lock_nested include/linux/fs.h:837 [inline] do_unlinkat+0x284/0x740 fs/namei.c:4369 __do_sys_unlinkat fs/namei.c:4425 [inline] __se_sys_unlinkat fs/namei.c:4418 [inline] __x64_sys_unlinkat+0xc1/0x130 fs/namei.c:4418 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x40/0x110 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b -> #1 (sb_writers#14){.+.+}-{0:0}: percpu_down_read include/linux/percpu-rwsem.h:51 [inline] __sb_start_write include/linux/fs.h:1635 [inline] sb_start_write include/linux/fs.h:1710 [inline] mnt_want_write_file+0x98/0x600 fs/namespace.c:448 reiserfs_ioctl+0x194/0x2e0 fs/reiserfs/ioctl.c:103 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:871 [inline] __se_sys_ioctl fs/ioctl.c:857 [inline] __x64_sys_ioctl+0x18f/0x210 fs/ioctl.c:857 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x40/0x110 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b -> #0 (&sbi->lock){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain kernel/locking/lockdep.c:3869 [inline] __lock_acquire+0x2433/0x3b20 kernel/locking/lockdep.c:5137 lock_acquire kernel/locking/lockdep.c:5754 [inline] lock_acquire+0x1ae/0x520 kernel/locking/lockdep.c:5719 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x175/0x9d0 kernel/locking/mutex.c:747 reiserfs_write_lock+0x79/0x100 fs/reiserfs/lock.c:27 reiserfs_lookup+0x184/0x690 fs/reiserfs/namei.c:364 lookup_one_qstr_excl+0x116/0x180 fs/namei.c:1609 do_unlinkat+0x29c/0x740 fs/namei.c:4370 __do_sys_unlinkat fs/namei.c:4425 [inline] __se_sys_unlinkat fs/namei.c:4418 [inline] __x64_sys_unlinkat+0xc1/0x130 fs/namei.c:4418 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x40/0x110 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b other info that might help us debug this: Chain exists of: &sbi->lock --> sb_writers#14 --> &type->i_mutex_dir_key#8/1 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&type->i_mutex_dir_key#8/1); lock(sb_writers#14); lock(&type->i_mutex_dir_key#8/1); lock(&sbi->lock); *** DEADLOCK *** 2 locks held by syz-executor.0/5488: #0: ffff8880796fa418 (sb_writers#14){.+.+}-{0:0}, at: do_unlinkat+0x1cf/0x740 fs/namei.c:4365 #1: ffff8880684d29c0 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:837 [inline] #1: ffff8880684d29c0 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: do_unlinkat+0x284/0x740 fs/namei.c:4369 stack backtrace: CPU: 0 PID: 5488 Comm: syz-executor.0 Not tainted 6.7.0-syzkaller-g0dd3ee311255 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xd9/0x1b0 lib/dump_stack.c:106 check_noncircular+0x317/0x400 kernel/locking/lockdep.c:2187 check_prev_add kernel/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain kernel/locking/lockdep.c:3869 [inline] __lock_acquire+0x2433/0x3b20 kernel/locking/lockdep.c:5137 lock_acquire kernel/locking/lockdep.c:5754 [inline] lock_acquire+0x1ae/0x520 kernel/locking/lockdep.c:5719 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x175/0x9d0 kernel/locking/mutex.c:747 reiserfs_write_lock+0x79/0x100 fs/reiserfs/lock.c:27 reiserfs_lookup+0x184/0x690 fs/reiserfs/namei.c:364 lookup_one_qstr_excl+0x116/0x180 fs/namei.c:1609 do_unlinkat+0x29c/0x740 fs/namei.c:4370 __do_sys_unlinkat fs/namei.c:4425 [inline] __se_sys_unlinkat fs/namei.c:4418 [inline] __x64_sys_unlinkat+0xc1/0x130 fs/namei.c:4418 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x40/0x110 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b RIP: 0033:0x7fd25927cce9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fd259f910c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000107 RAX: ffffffffffffffda RBX: 00007fd25939bf80 RCX: 00007fd25927cce9 RDX: 0000000000000000 RSI: 0000000020000000 RDI: 0000000000000005 RBP: 00007fd2592c947a R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 000000000000000b R14: 00007fd25939bf80 R15: 00007ffc291a2368