EXT4-fs: Warning: mounting with an experimental mount option 'dioread_nolock' for blocksize < PAGE_SIZE EXT4-fs (loop0): mounted filesystem 00000000-0000-0000-0000-000000000000 without journal. Quota mode: none. ====================================================== WARNING: possible circular locking dependency detected 6.3.0-rc4-syzkaller-00011-g59caa87f9dfb #0 Not tainted ------------------------------------------------------ syz-executor.0/6514 is trying to acquire lock: ffff0000e06432f0 (&ei->xattr_sem){++++}-{3:3}, at: ext4_find_inline_entry+0xe0/0x4bc fs/ext4/inline.c:1688 but task is already holding lock: ffff0000e0644030 (&ea_inode->i_rwsem#8/1){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline] ffff0000e0644030 (&ea_inode->i_rwsem#8/1){+.+.}-{3:3}, at: vfs_unlink+0xd8/0x508 fs/namei.c:4239 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&ea_inode->i_rwsem#8/1){+.+.}-{3:3}: down_write+0x5c/0xcc kernel/locking/rwsem.c:1573 inode_lock include/linux/fs.h:758 [inline] ext4_xattr_inode_create fs/ext4/xattr.c:1525 [inline] ext4_xattr_inode_lookup_create fs/ext4/xattr.c:1608 [inline] ext4_xattr_set_entry+0x2394/0x2c3c fs/ext4/xattr.c:1737 ext4_xattr_ibody_set+0x104/0x328 fs/ext4/xattr.c:2289 ext4_xattr_set_handle+0xa30/0x12d8 fs/ext4/xattr.c:2446 ext4_xattr_set+0x1e0/0x354 fs/ext4/xattr.c:2560 ext4_xattr_trusted_set+0x4c/0x64 fs/ext4/xattr_trusted.c:38 __vfs_setxattr+0x3d8/0x400 fs/xattr.c:203 __vfs_setxattr_noperm+0x110/0x528 fs/xattr.c:237 __vfs_setxattr_locked+0x1ec/0x218 fs/xattr.c:298 vfs_setxattr+0x1a8/0x344 fs/xattr.c:324 do_setxattr fs/xattr.c:609 [inline] setxattr+0x208/0x29c fs/xattr.c:632 path_setxattr+0x17c/0x258 fs/xattr.c:651 __do_sys_lsetxattr fs/xattr.c:674 [inline] __se_sys_lsetxattr fs/xattr.c:670 [inline] __arm64_sys_lsetxattr+0xbc/0xd8 fs/xattr.c:670 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x64/0x198 arch/arm64/kernel/syscall.c:193 el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:591 -> #0 (&ei->xattr_sem){++++}-{3:3}: check_prev_add kernel/locking/lockdep.c:3098 [inline] check_prevs_add kernel/locking/lockdep.c:3217 [inline] validate_chain kernel/locking/lockdep.c:3832 [inline] __lock_acquire+0x3338/0x764c kernel/locking/lockdep.c:5056 lock_acquire+0x238/0x718 kernel/locking/lockdep.c:5669 down_read+0x5c/0x78 kernel/locking/rwsem.c:1520 ext4_find_inline_entry+0xe0/0x4bc fs/ext4/inline.c:1688 __ext4_find_entry+0x270/0x15f8 fs/ext4/namei.c:1596 ext4_find_entry fs/ext4/namei.c:1730 [inline] __ext4_unlink+0x128/0x998 fs/ext4/namei.c:3220 ext4_unlink+0x1b4/0x6a0 fs/ext4/namei.c:3298 vfs_unlink+0x2f0/0x508 fs/namei.c:4250 do_unlinkat+0x4c8/0x82c fs/namei.c:4316 __do_sys_unlinkat fs/namei.c:4359 [inline] __se_sys_unlinkat fs/namei.c:4352 [inline] __arm64_sys_unlinkat+0xcc/0xfc fs/namei.c:4352 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x64/0x198 arch/arm64/kernel/syscall.c:193 el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:591 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&ea_inode->i_rwsem#8/1); lock(&ei->xattr_sem); lock(&ea_inode->i_rwsem#8/1); lock(&ei->xattr_sem); *** DEADLOCK *** 3 locks held by syz-executor.0/6514: #0: ffff0000da996460 (sb_writers#3){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:394 #1: ffff0000e0643628 (&type->i_mutex_dir_key#3/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline] #1: ffff0000e0643628 (&type->i_mutex_dir_key#3/1){+.+.}-{3:3}, at: do_unlinkat+0x2cc/0x82c fs/namei.c:4301 #2: ffff0000e0644030 (&ea_inode->i_rwsem#8/1){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline] #2: ffff0000e0644030 (&ea_inode->i_rwsem#8/1){+.+.}-{3:3}, at: vfs_unlink+0xd8/0x508 fs/namei.c:4239 stack backtrace: CPU: 1 PID: 6514 Comm: syz-executor.0 Not tainted 6.3.0-rc4-syzkaller-00011-g59caa87f9dfb #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023 Call trace: dump_backtrace+0x1b8/0x1e4 arch/arm64/kernel/stacktrace.c:158 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165 __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:2056 check_noncircular+0x2cc/0x378 kernel/locking/lockdep.c:2178 check_prev_add kernel/locking/lockdep.c:3098 [inline] check_prevs_add kernel/locking/lockdep.c:3217 [inline] validate_chain kernel/locking/lockdep.c:3832 [inline] __lock_acquire+0x3338/0x764c kernel/locking/lockdep.c:5056 lock_acquire+0x238/0x718 kernel/locking/lockdep.c:5669 down_read+0x5c/0x78 kernel/locking/rwsem.c:1520 ext4_find_inline_entry+0xe0/0x4bc fs/ext4/inline.c:1688 __ext4_find_entry+0x270/0x15f8 fs/ext4/namei.c:1596 ext4_find_entry fs/ext4/namei.c:1730 [inline] __ext4_unlink+0x128/0x998 fs/ext4/namei.c:3220 ext4_unlink+0x1b4/0x6a0 fs/ext4/namei.c:3298 vfs_unlink+0x2f0/0x508 fs/namei.c:4250 do_unlinkat+0x4c8/0x82c fs/namei.c:4316 __do_sys_unlinkat fs/namei.c:4359 [inline] __se_sys_unlinkat fs/namei.c:4352 [inline] __arm64_sys_unlinkat+0xcc/0xfc fs/namei.c:4352 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x64/0x198 arch/arm64/kernel/syscall.c:193 el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:591