====================================================== WARNING: possible circular locking dependency detected 6.5.0-rc1-syzkaller-00033-geb26cbb1a754 #0 Not tainted ------------------------------------------------------ syz-executor.4/21597 is trying to acquire lock: ffff88803d022090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x7a/0xd0 fs/reiserfs/lock.c:27 but task is already holding lock: ffff888079146640 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:806 [inline] ffff888079146640 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}, at: filename_create+0x260/0x530 fs/namei.c:3886 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}: down_write_nested+0x3d/0x50 kernel/locking/rwsem.c:1689 inode_lock_nested include/linux/fs.h:806 [inline] filename_create+0x260/0x530 fs/namei.c:3886 do_mkdirat+0xb7/0x520 fs/namei.c:4132 __do_sys_mkdirat fs/namei.c:4155 [inline] __se_sys_mkdirat fs/namei.c:4153 [inline] __x64_sys_mkdirat+0x89/0xa0 fs/namei.c:4153 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #1 (sb_writers#29){.+.+}-{0:0}: percpu_down_read include/linux/percpu-rwsem.h:51 [inline] __sb_start_write include/linux/fs.h:1494 [inline] sb_start_write+0x4d/0x1c0 include/linux/fs.h:1569 mnt_want_write_file+0x61/0x200 fs/namespace.c:447 reiserfs_ioctl+0x177/0x350 fs/reiserfs/ioctl.c:103 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:870 [inline] __se_sys_ioctl+0xf8/0x170 fs/ioctl.c:856 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #0 (&sbi->lock){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3142 [inline] check_prevs_add kernel/locking/lockdep.c:3261 [inline] validate_chain kernel/locking/lockdep.c:3876 [inline] __lock_acquire+0x39ff/0x7f70 kernel/locking/lockdep.c:5144 lock_acquire+0x1e3/0x520 kernel/locking/lockdep.c:5761 __mutex_lock_common+0x1d8/0x2530 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x1b/0x20 kernel/locking/mutex.c:799 reiserfs_write_lock+0x7a/0xd0 fs/reiserfs/lock.c:27 reiserfs_lookup+0x162/0x580 fs/reiserfs/namei.c:364 lookup_one_qstr_excl+0x11b/0x250 fs/namei.c:1605 filename_create+0x297/0x530 fs/namei.c:3887 do_mkdirat+0xb7/0x520 fs/namei.c:4132 __do_sys_mkdirat fs/namei.c:4155 [inline] __se_sys_mkdirat fs/namei.c:4153 [inline] __x64_sys_mkdirat+0x89/0xa0 fs/namei.c:4153 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd other info that might help us debug this: Chain exists of: &sbi->lock --> sb_writers#29 --> &type->i_mutex_dir_key#20/1 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&type->i_mutex_dir_key#20/1); lock(sb_writers#29); lock(&type->i_mutex_dir_key#20/1); lock(&sbi->lock); *** DEADLOCK *** 2 locks held by syz-executor.4/21597: #0: ffff88807851c410 (sb_writers#29){.+.+}-{0:0}, at: mnt_want_write+0x3f/0x90 fs/namespace.c:403 #1: ffff888079146640 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:806 [inline] #1: ffff888079146640 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}, at: filename_create+0x260/0x530 fs/namei.c:3886 stack backtrace: CPU: 0 PID: 21597 Comm: syz-executor.4 Not tainted 6.5.0-rc1-syzkaller-00033-geb26cbb1a754 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/03/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106 check_noncircular+0x375/0x4a0 kernel/locking/lockdep.c:2195 check_prev_add kernel/locking/lockdep.c:3142 [inline] check_prevs_add kernel/locking/lockdep.c:3261 [inline] validate_chain kernel/locking/lockdep.c:3876 [inline] __lock_acquire+0x39ff/0x7f70 kernel/locking/lockdep.c:5144 lock_acquire+0x1e3/0x520 kernel/locking/lockdep.c:5761 __mutex_lock_common+0x1d8/0x2530 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x1b/0x20 kernel/locking/mutex.c:799 reiserfs_write_lock+0x7a/0xd0 fs/reiserfs/lock.c:27 reiserfs_lookup+0x162/0x580 fs/reiserfs/namei.c:364 lookup_one_qstr_excl+0x11b/0x250 fs/namei.c:1605 filename_create+0x297/0x530 fs/namei.c:3887 do_mkdirat+0xb7/0x520 fs/namei.c:4132 __do_sys_mkdirat fs/namei.c:4155 [inline] __se_sys_mkdirat fs/namei.c:4153 [inline] __x64_sys_mkdirat+0x89/0xa0 fs/namei.c:4153 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7fe1ae47b627 Code: 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 02 01 00 00 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:00007fe1a4fdcee8 EFLAGS: 00000246 ORIG_RAX: 0000000000000102 RAX: ffffffffffffffda RBX: 0000000020000000 RCX: 00007fe1ae47b627 RDX: 00000000000001ff RSI: 0000000020000100 RDI: 00000000ffffff9c RBP: 00000000200000c0 R08: 0000000000000001 R09: 0000000000000000 R10: 00000000200000c0 R11: 0000000000000246 R12: 0000000020000100 R13: 00007fe1a4fdcf40 R14: 0000000000000000 R15: 0000000020000680 REISERFS warning (device loop4): reiserfs-15100 reiserfs_get_unused_objectid: no more object ids