REISERFS (device loop0): checking transaction log (loop0) REISERFS (device loop0): Using r5 hash to sort names REISERFS (device loop0): Created .reiserfs_priv - reserved for xattr storage. ====================================================== WARNING: possible circular locking dependency detected 6.1.141-syzkaller #0 Not tainted ------------------------------------------------------ syz.0.254/5407 is trying to acquire lock: ffff888057c102e0 (&type->i_mutex_dir_key#15){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline] ffff888057c102e0 (&type->i_mutex_dir_key#15){+.+.}-{3:3}, at: open_last_lookups fs/namei.c:3547 [inline] ffff888057c102e0 (&type->i_mutex_dir_key#15){+.+.}-{3:3}, at: path_openat+0x7c2/0x2e70 fs/namei.c:3780 but task is already holding lock: ffff88804fe24460 (sb_writers#22){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:393 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (sb_writers#22){.+.+}-{0:0}: percpu_down_read include/linux/percpu-rwsem.h:51 [inline] __sb_start_write include/linux/fs.h:1891 [inline] sb_start_write+0x4d/0x1c0 include/linux/fs.h:1966 mnt_want_write_file+0x5c/0x200 fs/namespace.c:437 reiserfs_ioctl+0x10a/0x330 fs/reiserfs/ioctl.c:103 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:870 [inline] __se_sys_ioctl+0xfa/0x170 fs/ioctl.c:856 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x68/0xd2 -> #1 (&sbi->lock){+.+.}-{3:3}: __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x120/0xaf0 kernel/locking/mutex.c:747 reiserfs_write_lock+0x75/0xd0 fs/reiserfs/lock.c:27 reiserfs_lookup+0x137/0x420 fs/reiserfs/namei.c:364 __lookup_slow+0x27d/0x3a0 fs/namei.c:1690 lookup_one_len+0x18e/0x2c0 fs/namei.c:2740 reiserfs_lookup_privroot+0x85/0x1e0 fs/reiserfs/xattr.c:973 reiserfs_fill_super+0x1f40/0x2340 fs/reiserfs/super.c:2174 mount_bdev+0x287/0x3c0 fs/super.c:1443 legacy_get_tree+0xe6/0x180 fs/fs_context.c:632 vfs_get_tree+0x88/0x270 fs/super.c:1573 do_new_mount+0x24a/0xa40 fs/namespace.c:3054 do_mount fs/namespace.c:3397 [inline] __do_sys_mount fs/namespace.c:3605 [inline] __se_sys_mount+0x2d6/0x3c0 fs/namespace.c:3582 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x68/0xd2 -> #0 (&type->i_mutex_dir_key#15){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain kernel/locking/lockdep.c:3825 [inline] __lock_acquire+0x2cf8/0x7c50 kernel/locking/lockdep.c:5049 lock_acquire+0x1b4/0x490 kernel/locking/lockdep.c:5662 down_write+0x36/0x60 kernel/locking/rwsem.c:1573 inode_lock include/linux/fs.h:758 [inline] open_last_lookups fs/namei.c:3547 [inline] path_openat+0x7c2/0x2e70 fs/namei.c:3780 do_filp_open+0x1c1/0x3c0 fs/namei.c:3810 do_sys_openat2+0x142/0x490 fs/open.c:1318 do_sys_open fs/open.c:1334 [inline] __do_sys_openat fs/open.c:1350 [inline] __se_sys_openat fs/open.c:1345 [inline] __x64_sys_openat+0x135/0x160 fs/open.c:1345 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x68/0xd2 other info that might help us debug this: Chain exists of: &type->i_mutex_dir_key#15 --> &sbi->lock --> sb_writers#22 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(sb_writers#22); lock(&sbi->lock); lock(sb_writers#22); lock(&type->i_mutex_dir_key#15); *** DEADLOCK *** 1 lock held by syz.0.254/5407: #0: ffff88804fe24460 (sb_writers#22){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:393 stack backtrace: CPU: 0 PID: 5407 Comm: syz.0.254 Not tainted 6.1.141-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 Call Trace: dump_stack_lvl+0x168/0x22e lib/dump_stack.c:106 check_noncircular+0x274/0x310 kernel/locking/lockdep.c:2170 check_prev_add kernel/locking/lockdep.c:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain kernel/locking/lockdep.c:3825 [inline] __lock_acquire+0x2cf8/0x7c50 kernel/locking/lockdep.c:5049 lock_acquire+0x1b4/0x490 kernel/locking/lockdep.c:5662 down_write+0x36/0x60 kernel/locking/rwsem.c:1573 inode_lock include/linux/fs.h:758 [inline] open_last_lookups fs/namei.c:3547 [inline] path_openat+0x7c2/0x2e70 fs/namei.c:3780 do_filp_open+0x1c1/0x3c0 fs/namei.c:3810 do_sys_openat2+0x142/0x490 fs/open.c:1318 do_sys_open fs/open.c:1334 [inline] __do_sys_openat fs/open.c:1350 [inline] __se_sys_openat fs/open.c:1345 [inline] __x64_sys_openat+0x135/0x160 fs/open.c:1345 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x68/0xd2 RIP: 0033:0x7fec6d18e929 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:00007fec6df1c038 EFLAGS: 00000246 ORIG_RAX: 0000000000000101 RAX: ffffffffffffffda RBX: 00007fec6d3b5fa0 RCX: 00007fec6d18e929 RDX: 0000000000143242 RSI: 0000200000000040 RDI: ffffffffffffff9c RBP: 00007fec6d210b39 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000080 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007fec6d3b5fa0 R15: 00007ffc425d73a8