syzbot

EXT4-fs (loop0): encrypted files will use data=ordered instead of data journaling mode
EXT4-fs (loop0): 1 truncate cleaned up
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.0.75/6032 is trying to acquire lock:
ffff88805523ca10 (&sb->s_type->i_mutex_key#9/1){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:804 [inline]
ffff88805523ca10 (&sb->s_type->i_mutex_key#9/1){+.+.}-{3:3}, at: ext4_xattr_inode_create fs/ext4/xattr.c:1516 [inline]
ffff88805523ca10 (&sb->s_type->i_mutex_key#9/1){+.+.}-{3:3}, at: ext4_xattr_inode_lookup_create+0x1975/0x1df0 fs/ext4/xattr.c:1598

but task is already holding lock:
ffff88805523be88 (&ei->i_data_sem/3){++++}-{3:3}, at: ext4_setattr+0x16e6/0x1dc0 fs/ext4/inode.c:5618

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&ei->i_data_sem/3){++++}-{3:3}:
       down_write+0x97/0x200 kernel/locking/rwsem.c:1573
       ext4_update_i_disksize fs/ext4/ext4.h:3394 [inline]
       ext4_xattr_inode_write fs/ext4/xattr.c:1454 [inline]
       ext4_xattr_inode_lookup_create+0x1653/0x1df0 fs/ext4/xattr.c:1604
       ext4_xattr_ibody_set+0x202/0x6a0 fs/ext4/xattr.c:2263
       ext4_xattr_set_handle+0xf59/0x14c0 fs/ext4/xattr.c:2440
       ext4_xattr_set+0x252/0x340 fs/ext4/xattr.c:2554
       __vfs_setxattr+0x431/0x470 fs/xattr.c:201
       __vfs_setxattr_noperm+0x12d/0x5e0 fs/xattr.c:235
       vfs_setxattr+0x16b/0x2f0 fs/xattr.c:322
       do_setxattr fs/xattr.c:630 [inline]
       path_setxattr+0x3f3/0x5d0 fs/xattr.c:659
       __do_sys_setxattr fs/xattr.c:677 [inline]
       __se_sys_setxattr fs/xattr.c:673 [inline]
       __x64_sys_setxattr+0xbb/0xd0 fs/xattr.c:673
       do_syscall_x64 arch/x86/entry/common.c:46 [inline]
       do_syscall_64+0x55/0xa0 arch/x86/entry/common.c:76
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #0 (&sb->s_type->i_mutex_key#9/1){+.+.}-{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+0x2df1/0x7d40 kernel/locking/lockdep.c:5137
       lock_acquire+0x19e/0x420 kernel/locking/lockdep.c:5754
       down_write+0x97/0x200 kernel/locking/rwsem.c:1573
       inode_lock include/linux/fs.h:804 [inline]
       ext4_xattr_inode_create fs/ext4/xattr.c:1516 [inline]
       ext4_xattr_inode_lookup_create+0x1975/0x1df0 fs/ext4/xattr.c:1598
       ext4_xattr_block_set+0x243/0x32b0 fs/ext4/xattr.c:1918
       ext4_xattr_move_to_block fs/ext4/xattr.c:2664 [inline]
       ext4_xattr_make_inode_space fs/ext4/xattr.c:2739 [inline]
       ext4_expand_extra_isize_ea+0x12c5/0x1e80 fs/ext4/xattr.c:2827
       __ext4_expand_extra_isize+0x306/0x400 fs/ext4/inode.c:5990
       ext4_try_to_expand_extra_isize fs/ext4/inode.c:6033 [inline]
       __ext4_mark_inode_dirty+0x45d/0x6e0 fs/ext4/inode.c:6111
       ext4_setattr+0x1762/0x1dc0 fs/ext4/inode.c:5621
       notify_change+0xb0d/0xe10 fs/attr.c:499
       do_truncate+0x1b0/0x240 fs/open.c:66
       handle_truncate fs/namei.c:3299 [inline]
       do_open fs/namei.c:3644 [inline]
       path_openat+0x2a32/0x3230 fs/namei.c:3797
       do_filp_open+0x1f5/0x430 fs/namei.c:3824
       do_sys_openat2+0x134/0x1d0 fs/open.c:1421
       do_sys_open fs/open.c:1436 [inline]
       __do_sys_openat fs/open.c:1452 [inline]
       __se_sys_openat fs/open.c:1447 [inline]
       __x64_sys_openat+0x139/0x160 fs/open.c:1447
       do_syscall_x64 arch/x86/entry/common.c:46 [inline]
       do_syscall_64+0x55/0xa0 arch/x86/entry/common.c:76
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&ei->i_data_sem/3);
                               lock(&sb->s_type->i_mutex_key#9/1);
                               lock(&ei->i_data_sem/3);
  lock(&sb->s_type->i_mutex_key#9/1);

 *** DEADLOCK ***

5 locks held by syz.0.75/6032:
 #0: ffff88807d824418 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:412
 #1: ffff88805523c010 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: inode_lock include/linux/fs.h:804 [inline]
 #1: ffff88805523c010 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: do_truncate+0x19c/0x240 fs/open.c:64
 #2: ffff88805523c1a0 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:849 [inline]
 #2: ffff88805523c1a0 (mapping.invalidate_lock#2){++++}-{3:3}, at: ext4_setattr+0xffe/0x1dc0 fs/ext4/inode.c:5566
 #3: ffff88805523be88 (&ei->i_data_sem/3){++++}-{3:3}, at: ext4_setattr+0x16e6/0x1dc0 fs/ext4/inode.c:5618
 #4: ffff88805523bcc8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_write_trylock_xattr fs/ext4/xattr.h:165 [inline]
 #4: ffff88805523bcc8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_try_to_expand_extra_isize fs/ext4/inode.c:6030 [inline]
 #4: ffff88805523bcc8 (&ei->xattr_sem){++++}-{3:3}, at: __ext4_mark_inode_dirty+0x3dc/0x6e0 fs/ext4/inode.c:6111

stack backtrace:
CPU: 1 PID: 6032 Comm: syz.0.75 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x18c/0x250 lib/dump_stack.c:106
 check_noncircular+0x2fc/0x400 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+0x2df1/0x7d40 kernel/locking/lockdep.c:5137
 lock_acquire+0x19e/0x420 kernel/locking/lockdep.c:5754
 down_write+0x97/0x200 kernel/locking/rwsem.c:1573
 inode_lock include/linux/fs.h:804 [inline]
 ext4_xattr_inode_create fs/ext4/xattr.c:1516 [inline]
 ext4_xattr_inode_lookup_create+0x1975/0x1df0 fs/ext4/xattr.c:1598
 ext4_xattr_block_set+0x243/0x32b0 fs/ext4/xattr.c:1918
 ext4_xattr_move_to_block fs/ext4/xattr.c:2664 [inline]
 ext4_xattr_make_inode_space fs/ext4/xattr.c:2739 [inline]
 ext4_expand_extra_isize_ea+0x12c5/0x1e80 fs/ext4/xattr.c:2827
 __ext4_expand_extra_isize+0x306/0x400 fs/ext4/inode.c:5990
 ext4_try_to_expand_extra_isize fs/ext4/inode.c:6033 [inline]
 __ext4_mark_inode_dirty+0x45d/0x6e0 fs/ext4/inode.c:6111
 ext4_setattr+0x1762/0x1dc0 fs/ext4/inode.c:5621
 notify_change+0xb0d/0xe10 fs/attr.c:499
 do_truncate+0x1b0/0x240 fs/open.c:66
 handle_truncate fs/namei.c:3299 [inline]
 do_open fs/namei.c:3644 [inline]
 path_openat+0x2a32/0x3230 fs/namei.c:3797
 do_filp_open+0x1f5/0x430 fs/namei.c:3824
 do_sys_openat2+0x134/0x1d0 fs/open.c:1421
 do_sys_open fs/open.c:1436 [inline]
 __do_sys_openat fs/open.c:1452 [inline]
 __se_sys_openat fs/open.c:1447 [inline]
 __x64_sys_openat+0x139/0x160 fs/open.c:1447
 do_syscall_x64 arch/x86/entry/common.c:46 [inline]
 do_syscall_64+0x55/0xa0 arch/x86/entry/common.c:76
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fb13cb9c819
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffd2ab777a8 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007fb13ce15fa0 RCX: 00007fb13cb9c819
RDX: 0000000000109342 RSI: 0000200000000040 RDI: ffffffffffffff9c
RBP: 00007fb13cc32c91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fb13ce15fac R14: 00007fb13ce15fa0 R15: 00007fb13ce15fa0
 </TASK>