REISERFS (device loop0): journal params: device loop0, size 512, journal first block 18, max trans len 256, max batch 225, max commit age 30, max trans age 30 REISERFS (device loop0): checking transaction log (loop0) REISERFS (device loop0): Using r5 hash to sort names reiserfs: enabling write barrier flush mode REISERFS (device loop0): Created .reiserfs_priv - reserved for xattr storage. ====================================================== WARNING: possible circular locking dependency detected 6.12.0-rc2-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.0/5409 is trying to acquire lock: ffff888022135090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x7b/0xe0 fs/reiserfs/lock.c:27 but task is already holding lock: ffff888076f502d8 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:850 [inline] ffff888076f502d8 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: do_unlinkat+0x26a/0x830 fs/namei.c:4520 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+0xa2/0x220 kernel/locking/rwsem.c:1693 inode_lock_nested include/linux/fs.h:850 [inline] do_unlinkat+0x26a/0x830 fs/namei.c:4520 __do_sys_unlinkat fs/namei.c:4576 [inline] __se_sys_unlinkat fs/namei.c:4569 [inline] __x64_sys_unlinkat+0xcc/0xf0 fs/namei.c:4569 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x82/0x160 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x76/0x7e -> #1 (sb_writers#13){.+.+}-{0:0}: percpu_down_read include/linux/percpu-rwsem.h:51 [inline] __sb_start_write include/linux/fs.h:1716 [inline] sb_start_write+0x4d/0x1c0 include/linux/fs.h:1852 mnt_want_write_file+0x5e/0x200 fs/namespace.c:559 reiserfs_ioctl+0x172/0x2f0 fs/reiserfs/ioctl.c:103 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:907 [inline] __se_sys_ioctl+0xf9/0x170 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x82/0x160 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x76/0x7e -> #0 (&sbi->lock){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3161 [inline] check_prevs_add kernel/locking/lockdep.c:3280 [inline] validate_chain kernel/locking/lockdep.c:3904 [inline] __lock_acquire+0x2f62/0x8080 kernel/locking/lockdep.c:5202 lock_acquire+0x1ed/0x540 kernel/locking/lockdep.c:5825 __mutex_lock_common kernel/locking/mutex.c:608 [inline] __mutex_lock+0x136/0xd70 kernel/locking/mutex.c:752 reiserfs_write_lock+0x7b/0xe0 fs/reiserfs/lock.c:27 reiserfs_lookup+0x162/0x580 fs/reiserfs/namei.c:364 lookup_one_qstr_excl+0x11f/0x260 fs/namei.c:1633 do_unlinkat+0x297/0x830 fs/namei.c:4521 __do_sys_unlinkat fs/namei.c:4576 [inline] __se_sys_unlinkat fs/namei.c:4569 [inline] __x64_sys_unlinkat+0xcc/0xf0 fs/namei.c:4569 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x82/0x160 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x76/0x7e other info that might help us debug this: Chain exists of: &sbi->lock --> sb_writers#13 --> &type->i_mutex_dir_key#8/1 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&type->i_mutex_dir_key#8/1); lock(sb_writers#13); lock(&type->i_mutex_dir_key#8/1); lock(&sbi->lock); *** DEADLOCK *** 2 locks held by syz-executor.0/5409: #0: ffff888022386420 (sb_writers#13){.+.+}-{0:0}, at: mnt_want_write+0x3f/0x90 fs/namespace.c:515 #1: ffff888076f502d8 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:850 [inline] #1: ffff888076f502d8 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: do_unlinkat+0x26a/0x830 fs/namei.c:4520 stack backtrace: CPU: 1 UID: 0 PID: 5409 Comm: syz-executor.0 Not tainted 6.12.0-rc2-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120 print_circular_bug+0x13a/0x1b0 kernel/locking/lockdep.c:2074 check_noncircular+0x379/0x4b0 kernel/locking/lockdep.c:2206 check_prev_add kernel/locking/lockdep.c:3161 [inline] check_prevs_add kernel/locking/lockdep.c:3280 [inline] validate_chain kernel/locking/lockdep.c:3904 [inline] __lock_acquire+0x2f62/0x8080 kernel/locking/lockdep.c:5202 lock_acquire+0x1ed/0x540 kernel/locking/lockdep.c:5825 __mutex_lock_common kernel/locking/mutex.c:608 [inline] __mutex_lock+0x136/0xd70 kernel/locking/mutex.c:752 reiserfs_write_lock+0x7b/0xe0 fs/reiserfs/lock.c:27 reiserfs_lookup+0x162/0x580 fs/reiserfs/namei.c:364 lookup_one_qstr_excl+0x11f/0x260 fs/namei.c:1633 do_unlinkat+0x297/0x830 fs/namei.c:4521 __do_sys_unlinkat fs/namei.c:4576 [inline] __se_sys_unlinkat fs/namei.c:4569 [inline] __x64_sys_unlinkat+0xcc/0xf0 fs/namei.c:4569 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x82/0x160 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7f7cb947cb29 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:00007f7cba24e0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000107 RAX: ffffffffffffffda RBX: 00007f7cb959bf80 RCX: 00007f7cb947cb29 RDX: 0000000000000000 RSI: 0000000020000000 RDI: 0000000000000005 RBP: 00007f7cb94c847a R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 000000000000000b R14: 00007f7cb959bf80 R15: 00007ffff5eb81d8