REISERFS (device loop3): Using tea hash to sort names REISERFS (device loop3): Created .reiserfs_priv - reserved for xattr storage. ====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.3.627/6395 is trying to acquire lock: ffff0000f6ac5260 (&type->i_mutex_dir_key#20){++++}-{3:3}, at: inode_lock include/linux/fs.h:764 [inline] ffff0000f6ac5260 (&type->i_mutex_dir_key#20){++++}-{3:3}, at: vfs_rename+0x6a8/0xe3c fs/namei.c:4890 but task is already holding lock: ffff0000f6ac5fa0 (&type->i_mutex_dir_key#20/2){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:799 [inline] ffff0000f6ac5fa0 (&type->i_mutex_dir_key#20/2){+.+.}-{3:3}, at: vfs_rename+0x648/0xe3c fs/namei.c:4888 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&type->i_mutex_dir_key#20/2){+.+.}-{3:3}: down_write_nested+0x64/0x94 kernel/locking/rwsem.c:1689 inode_lock_nested include/linux/fs.h:799 [inline] xattr_rmdir fs/reiserfs/xattr.c:106 [inline] delete_one_xattr+0xe8/0x2c8 fs/reiserfs/xattr.c:338 reiserfs_for_each_xattr+0x5d0/0x6f8 fs/reiserfs/xattr.c:311 reiserfs_delete_xattrs+0x2c/0xa4 fs/reiserfs/xattr.c:364 reiserfs_evict_inode+0x1f0/0x408 fs/reiserfs/inode.c:53 evict+0x3d8/0x824 fs/inode.c:705 iput_final fs/inode.c:1834 [inline] iput+0x728/0x7e8 fs/inode.c:1860 d_delete_notify include/linux/fsnotify.h:267 [inline] vfs_rmdir+0x32c/0x438 fs/namei.c:4255 do_rmdir+0x244/0x524 fs/namei.c:4303 __do_sys_unlinkat fs/namei.c:4483 [inline] __se_sys_unlinkat fs/namei.c:4477 [inline] __arm64_sys_unlinkat+0xcc/0xfc fs/namei.c:4477 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x290 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x13c/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x5c/0x134 arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x128 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585 -> #1 (&type->i_mutex_dir_key#20/3){+.+.}-{3:3}: down_write_nested+0x64/0x94 kernel/locking/rwsem.c:1689 inode_lock_nested include/linux/fs.h:799 [inline] open_xa_root fs/reiserfs/xattr.c:127 [inline] open_xa_dir+0x124/0x5ec fs/reiserfs/xattr.c:152 xattr_lookup+0x3c/0x268 fs/reiserfs/xattr.c:395 reiserfs_xattr_set_handle+0xe8/0xdbc fs/reiserfs/xattr.c:533 reiserfs_xattr_set+0x3a8/0x4d4 fs/reiserfs/xattr.c:633 trusted_set+0x98/0xe8 fs/reiserfs/xattr_trusted.c:31 __vfs_setxattr+0x374/0x390 fs/xattr.c:182 __vfs_setxattr_noperm+0x120/0x56c fs/xattr.c:216 __vfs_setxattr_locked+0x1e8/0x214 fs/xattr.c:277 vfs_setxattr+0x158/0x2a8 fs/xattr.c:309 do_setxattr fs/xattr.c:594 [inline] setxattr+0x258/0x2d8 fs/xattr.c:617 path_setxattr+0x130/0x260 fs/xattr.c:636 __do_sys_setxattr fs/xattr.c:652 [inline] __se_sys_setxattr fs/xattr.c:648 [inline] __arm64_sys_setxattr+0xc4/0xe0 fs/xattr.c:648 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x290 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x13c/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x5c/0x134 arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x128 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585 -> #0 (&type->i_mutex_dir_key#20){++++}-{3:3}: check_prev_add kernel/locking/lockdep.c:3095 [inline] check_prevs_add kernel/locking/lockdep.c:3214 [inline] validate_chain kernel/locking/lockdep.c:3830 [inline] __lock_acquire+0x2808/0x6634 kernel/locking/lockdep.c:5063 lock_acquire+0x20c/0x638 kernel/locking/lockdep.c:5676 down_write+0x5c/0x88 kernel/locking/rwsem.c:1573 inode_lock include/linux/fs.h:764 [inline] vfs_rename+0x6a8/0xe3c fs/namei.c:4890 do_renameat2+0x760/0xaa4 fs/namei.c:5078 __do_sys_renameat2 fs/namei.c:5111 [inline] __se_sys_renameat2 fs/namei.c:5108 [inline] __arm64_sys_renameat2+0xe8/0x104 fs/namei.c:5108 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x290 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x13c/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x5c/0x134 arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x128 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585 other info that might help us debug this: Chain exists of: &type->i_mutex_dir_key#20 --> &type->i_mutex_dir_key#20/3 --> &type->i_mutex_dir_key#20/2 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&type->i_mutex_dir_key#20/2); lock(&type->i_mutex_dir_key#20/3); lock(&type->i_mutex_dir_key#20/2); lock(&type->i_mutex_dir_key#20); *** DEADLOCK *** 5 locks held by syz.3.627/6395: #0: ffff0000ce91c460 (sb_writers#33){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:402 #1: ffff0000ce91c748 (&type->s_vfs_rename_key#6){+.+.}-{3:3}, at: lock_rename fs/namei.c:3089 [inline] #1: ffff0000ce91c748 (&type->s_vfs_rename_key#6){+.+.}-{3:3}, at: do_renameat2+0x314/0xaa4 fs/namei.c:5017 #2: ffff0000f6ac4520 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:799 [inline] #2: ffff0000f6ac4520 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}, at: lock_two_directories fs/namei.c:-1 [inline] #2: ffff0000f6ac4520 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}, at: lock_rename fs/namei.c:3090 [inline] #2: ffff0000f6ac4520 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}, at: do_renameat2+0x390/0xaa4 fs/namei.c:5017 #3: ffff0000f6ac5900 (&type->i_mutex_dir_key#20/5){+.+.}-{3:3}, at: lock_rename include/linux/fs.h:-1 [inline] #3: ffff0000f6ac5900 (&type->i_mutex_dir_key#20/5){+.+.}-{3:3}, at: do_renameat2+0x3c4/0xaa4 fs/namei.c:5017 #4: ffff0000f6ac5fa0 (&type->i_mutex_dir_key#20/2){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:799 [inline] #4: ffff0000f6ac5fa0 (&type->i_mutex_dir_key#20/2){+.+.}-{3:3}, at: vfs_rename+0x648/0xe3c fs/namei.c:4888 stack backtrace: CPU: 0 PID: 6395 Comm: syz.3.627 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/14/2026 Call trace: dump_backtrace+0x1c4/0x1f0 arch/arm64/kernel/stacktrace.c:158 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165 __dump_stack+0x30/0x40 lib/dump_stack.c:88 dump_stack_lvl+0xf4/0x15c lib/dump_stack.c:106 dump_stack+0x1c/0x5c lib/dump_stack.c:113 print_circular_bug+0x148/0x1b0 kernel/locking/lockdep.c:2048 check_noncircular+0x264/0x2f8 kernel/locking/lockdep.c:2170 check_prev_add kernel/locking/lockdep.c:3095 [inline] check_prevs_add kernel/locking/lockdep.c:3214 [inline] validate_chain kernel/locking/lockdep.c:3830 [inline] __lock_acquire+0x2808/0x6634 kernel/locking/lockdep.c:5063 lock_acquire+0x20c/0x638 kernel/locking/lockdep.c:5676 down_write+0x5c/0x88 kernel/locking/rwsem.c:1573 inode_lock include/linux/fs.h:764 [inline] vfs_rename+0x6a8/0xe3c fs/namei.c:4890 do_renameat2+0x760/0xaa4 fs/namei.c:5078 __do_sys_renameat2 fs/namei.c:5111 [inline] __se_sys_renameat2 fs/namei.c:5108 [inline] __arm64_sys_renameat2+0xe8/0x104 fs/namei.c:5108 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x290 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x13c/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x5c/0x134 arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x128 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585