======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Tainted: G             L     
------------------------------------------------------
syz.3.384/8138 is trying to acquire lock:
ffff8881bb18b900 (&ei->xattr_sem){++++}-{4:4}, at: ext4_destroy_inline_data+0x28/0xe0

but task is already holding lock:
ffff8881bdb78c18 (&sbi->s_writepages_rwsem){++++}-{0:0}, at: ext4_writepages+0x205/0x3b0

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&sbi->s_writepages_rwsem){++++}-{0:0}:
       percpu_down_read_internal+0x48/0x1c0
       ext4_writepages+0x205/0x3b0
       do_writepages+0x338/0x560
       __writeback_single_inode+0x12e/0xf90
       writeback_single_inode+0x4ef/0xe70
       write_inode_now+0x1c2/0x290
       iput+0x98b/0xf00
       ext4_xattr_block_set+0x1b0c/0x2a80
       ext4_expand_extra_isize_ea+0x1342/0x1e70
       __ext4_expand_extra_isize+0x30d/0x400
       __ext4_mark_inode_dirty+0x455/0x700
       ext4_evict_inode+0x976/0x10c0
       evict+0x624/0xb50
       ext4_orphan_cleanup+0xc7a/0x14c0
       ext4_fill_super+0x5cb4/0x65c0
       get_tree_bdev_flags+0x430/0x4f0
       vfs_get_tree+0x92/0x2a0
       do_new_mount+0x319/0xdc0
       __se_sys_mount+0x31d/0x420
       do_syscall_64+0x174/0x580
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&ei->xattr_sem){++++}-{4:4}:
       __lock_acquire+0x15ff/0x2e50
       lock_acquire+0x115/0x350
       down_write+0x96/0x200
       ext4_destroy_inline_data+0x28/0xe0
       ext4_do_writepages+0x573/0x47a0
       ext4_writepages+0x241/0x3b0
       do_writepages+0x338/0x560
       filemap_flush+0x1e1/0x2e0
       ext4_convert_inline_data+0x189/0x5c0
       ext4_setattr+0xef1/0x1d70
       notify_change+0xbba/0xea0
       do_truncate+0x1c2/0x250
       vfs_truncate+0x4b4/0x540
       ksys_truncate+0xf3/0x1c0
       __x64_sys_truncate+0x5b/0x70
       do_syscall_64+0x174/0x580
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  rlock(&sbi->s_writepages_rwsem);
                               lock(&ei->xattr_sem);
                               lock(&sbi->s_writepages_rwsem);
  lock(&ei->xattr_sem);

 *** DEADLOCK ***

3 locks held by syz.3.384/8138:
 #0: ffff88816cb68450 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90
 #1: ffff8881bb18bbc0 (&sb->s_type->i_mutex_key#11){++++}-{4:4}, at: do_truncate+0x18f/0x250
 #2: ffff8881bdb78c18 (&sbi->s_writepages_rwsem){++++}-{0:0}, at: ext4_writepages+0x205/0x3b0

stack backtrace:
CPU: 0 UID: 0 PID: 8138 Comm: syz.3.384 Tainted: G             L      syzkaller #0 PREEMPT(full) 
Tainted: [L]=SOFTLOCKUP
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150
 print_circular_bug+0x2e2/0x300
 check_noncircular+0x12f/0x150
 __lock_acquire+0x15ff/0x2e50
 lock_acquire+0x115/0x350
 down_write+0x96/0x200
 ext4_destroy_inline_data+0x28/0xe0
 ext4_do_writepages+0x573/0x47a0
 ext4_writepages+0x241/0x3b0
 do_writepages+0x338/0x560
 filemap_flush+0x1e1/0x2e0
 ext4_convert_inline_data+0x189/0x5c0
 ext4_setattr+0xef1/0x1d70
 notify_change+0xbba/0xea0
 do_truncate+0x1c2/0x250
 vfs_truncate+0x4b4/0x540
 ksys_truncate+0xf3/0x1c0
 __x64_sys_truncate+0x5b/0x70
 do_syscall_64+0x174/0x580
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f21dbb9e0d9
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:00007f21dca56028 EFLAGS: 00000246 ORIG_RAX: 000000000000004c
RAX: ffffffffffffffda RBX: 00007f21dbe26090 RCX: 00007f21dbb9e0d9
RDX: 0000000000000000 RSI: 0000000002fffffd RDI: 0000200000000940
RBP: 00007f21dbc35024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f21dbe26128 R14: 00007f21dbe26090 R15: 00007ffddc0b0b88
 </TASK>
EXT4-fs error (device loop3): ext4_mb_generate_buddy:1317: group 0, block bitmap and bg descriptor inconsistent: 25 vs 281 free clusters
EXT4-fs (loop3): Delayed block allocation failed for inode 15 at logical offset 0 with max blocks 1 with error 28
EXT4-fs (loop3): This should not happen!! Data will be lost

EXT4-fs (loop3): Total free blocks count 0
EXT4-fs (loop3): Free/Dirty block details
EXT4-fs (loop3): free_blocks=4096
EXT4-fs (loop3): dirty_blocks=32
EXT4-fs (loop3): Block reservation details
EXT4-fs (loop3): i_reserved_data_blocks=2
EXT4-fs error (device loop3) in ext4_setattr:6172: error 28
