REISERFS (device loop4): Using tea hash to sort names
REISERFS (device loop4): Created .reiserfs_priv - reserved for xattr storage.
======================================================
WARNING: possible circular locking dependency detected
6.7.0-rc8-syzkaller-g0802e17d9aca #0 Not tainted
------------------------------------------------------
syz-executor.4/14677 is trying to acquire lock:
ffff00012824aaa0 (&type->i_mutex_dir_key#9/3){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:837 [inline]
ffff00012824aaa0 (&type->i_mutex_dir_key#9/3){+.+.}-{3:3}, at: open_xa_root fs/reiserfs/xattr.c:128 [inline]
ffff00012824aaa0 (&type->i_mutex_dir_key#9/3){+.+.}-{3:3}, at: open_xa_dir+0x11c/0x578 fs/reiserfs/xattr.c:153
but task is already holding lock:
ffff000125ef6090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock_nested+0x68/0xd8 fs/reiserfs/lock.c:78
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #1 (&sbi->lock){+.+.}-{3:3}:
__mutex_lock_common+0x190/0x21a0 kernel/locking/mutex.c:603
__mutex_lock kernel/locking/mutex.c:747 [inline]
mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:799
reiserfs_write_lock+0x7c/0xe8 fs/reiserfs/lock.c:27
reiserfs_mkdir+0x280/0x77c fs/reiserfs/namei.c:829
xattr_mkdir fs/reiserfs/xattr.c:77 [inline]
open_xa_root fs/reiserfs/xattr.c:137 [inline]
open_xa_dir+0x288/0x578 fs/reiserfs/xattr.c:153
xattr_lookup+0x3c/0x268 fs/reiserfs/xattr.c:396
reiserfs_xattr_set_handle+0xe0/0xe94 fs/reiserfs/xattr.c:535
reiserfs_security_write+0x13c/0x1d0 fs/reiserfs/xattr_security.c:107
reiserfs_new_inode+0x1084/0x1698 fs/reiserfs/inode.c:2105
reiserfs_create+0x33c/0x5a4 fs/reiserfs/namei.c:666
vfs_create+0x21c/0x340 fs/namei.c:3179
do_mknodat+0x3c4/0x564 fs/namei.c:4034
__do_sys_mknodat fs/namei.c:4062 [inline]
__se_sys_mknodat fs/namei.c:4059 [inline]
__arm64_sys_mknodat+0xb0/0xcc fs/namei.c:4059
__invoke_syscall arch/arm64/kernel/syscall.c:37 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:51
el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:136
do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:155
el0_svc+0x54/0x158 arch/arm64/kernel/entry-common.c:678
el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:696
el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:595
-> #0 (&type->i_mutex_dir_key#9/3){+.+.}-{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+0x3384/0x763c kernel/locking/lockdep.c:5137
lock_acquire+0x23c/0x71c kernel/locking/lockdep.c:5754
down_write_nested+0x58/0xcc kernel/locking/rwsem.c:1695
inode_lock_nested include/linux/fs.h:837 [inline]
open_xa_root fs/reiserfs/xattr.c:128 [inline]
open_xa_dir+0x11c/0x578 fs/reiserfs/xattr.c:153
xattr_lookup+0x3c/0x268 fs/reiserfs/xattr.c:396
reiserfs_xattr_get+0xf0/0x96c fs/reiserfs/xattr.c:679
security_get+0x94/0xd0 fs/reiserfs/xattr_security.c:19
__vfs_getxattr+0x394/0x3c0 fs/xattr.c:424
smk_fetch+0xc8/0x150 security/smack/smack_lsm.c:304
smack_d_instantiate+0x594/0x880 security/smack/smack_lsm.c:3573
security_d_instantiate+0x98/0xf0 security/security.c:3799
d_instantiate_new+0x64/0x120 fs/dcache.c:2052
reiserfs_create+0x520/0x5a4 fs/reiserfs/namei.c:692
vfs_create+0x21c/0x340 fs/namei.c:3179
do_mknodat+0x3c4/0x564 fs/namei.c:4034
__do_sys_mknodat fs/namei.c:4062 [inline]
__se_sys_mknodat fs/namei.c:4059 [inline]
__arm64_sys_mknodat+0xb0/0xcc fs/namei.c:4059
__invoke_syscall arch/arm64/kernel/syscall.c:37 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:51
el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:136
do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:155
el0_svc+0x54/0x158 arch/arm64/kernel/entry-common.c:678
el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:696
el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:595
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(&sbi->lock);
lock(&type->i_mutex_dir_key#9/3);
lock(&sbi->lock);
lock(&type->i_mutex_dir_key#9/3);
*** DEADLOCK ***
3 locks held by syz-executor.4/14677:
#0: ffff0000d91b4418 (sb_writers#20){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:404
#1: ffff00012824b140 (&type->i_mutex_dir_key#9/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:837 [inline]
#1: ffff00012824b140 (&type->i_mutex_dir_key#9/1){+.+.}-{3:3}, at: filename_create+0x204/0x468 fs/namei.c:3875
#2: ffff000125ef6090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock_nested+0x68/0xd8 fs/reiserfs/lock.c:78
stack backtrace:
CPU: 0 PID: 14677 Comm: syz-executor.4 Not tainted 6.7.0-rc8-syzkaller-g0802e17d9aca #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
Call trace:
dump_backtrace+0x1b8/0x1e4 arch/arm64/kernel/stacktrace.c:291
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:298
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xd0/0x124 lib/dump_stack.c:106
dump_stack+0x1c/0x28 lib/dump_stack.c:113
print_circular_bug+0x150/0x1b8 kernel/locking/lockdep.c:2060
check_noncircular+0x310/0x404 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+0x3384/0x763c kernel/locking/lockdep.c:5137
lock_acquire+0x23c/0x71c kernel/locking/lockdep.c:5754
down_write_nested+0x58/0xcc kernel/locking/rwsem.c:1695
inode_lock_nested include/linux/fs.h:837 [inline]
open_xa_root fs/reiserfs/xattr.c:128 [inline]
open_xa_dir+0x11c/0x578 fs/reiserfs/xattr.c:153
xattr_lookup+0x3c/0x268 fs/reiserfs/xattr.c:396
reiserfs_xattr_get+0xf0/0x96c fs/reiserfs/xattr.c:679
security_get+0x94/0xd0 fs/reiserfs/xattr_security.c:19
__vfs_getxattr+0x394/0x3c0 fs/xattr.c:424
smk_fetch+0xc8/0x150 security/smack/smack_lsm.c:304
smack_d_instantiate+0x594/0x880 security/smack/smack_lsm.c:3573
security_d_instantiate+0x98/0xf0 security/security.c:3799
d_instantiate_new+0x64/0x120 fs/dcache.c:2052
reiserfs_create+0x520/0x5a4 fs/reiserfs/namei.c:692
vfs_create+0x21c/0x340 fs/namei.c:3179
do_mknodat+0x3c4/0x564 fs/namei.c:4034
__do_sys_mknodat fs/namei.c:4062 [inline]
__se_sys_mknodat fs/namei.c:4059 [inline]
__arm64_sys_mknodat+0xb0/0xcc fs/namei.c:4059
__invoke_syscall arch/arm64/kernel/syscall.c:37 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:51
el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:136
do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:155
el0_svc+0x54/0x158 arch/arm64/kernel/entry-common.c:678
el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:696
el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:595