======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.4.1550/10209 is trying to acquire lock:
ffff88801ed4d6d8 (&ei->xattr_sem){++++}-{4:4}, at: ext4_destroy_inline_data+0x28/0xe0

but task is already holding lock:
ffff888107772b98 (&sbi->s_writepages_rwsem){++++}-{0:0}, at: ext4_writepages+0x1cc/0x350

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&sbi->s_writepages_rwsem){++++}-{0:0}:
       lock_acquire+0x120/0x360
       percpu_down_read_internal+0x48/0x1c0
       ext4_writepages+0x1cc/0x350
       do_writepages+0x32e/0x550
       __writeback_single_inode+0x145/0xff0
       writeback_single_inode+0x1f9/0x6a0
       write_inode_now+0x160/0x1d0
       iput+0x830/0xc50
       ext4_xattr_block_set+0x1fce/0x2ac0
       ext4_expand_extra_isize_ea+0x12da/0x1ea0
       __ext4_expand_extra_isize+0x30d/0x400
       __ext4_mark_inode_dirty+0x46c/0x700
       ext4_evict_inode+0x80d/0xee0
       evict+0x504/0x9c0
       ext4_orphan_cleanup+0xc20/0x1460
       ext4_fill_super+0x5920/0x61e0
       get_tree_bdev_flags+0x40e/0x4d0
       vfs_get_tree+0x92/0x2b0
       do_new_mount+0x302/0xa10
       __se_sys_mount+0x313/0x410
       do_syscall_64+0xfa/0xfa0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&ei->xattr_sem){++++}-{4:4}:
       validate_chain+0xb9b/0x2140
       __lock_acquire+0xab9/0xd20
       lock_acquire+0x120/0x360
       down_write+0x96/0x1f0
       ext4_destroy_inline_data+0x28/0xe0
       ext4_do_writepages+0x526/0x4610
       ext4_writepages+0x205/0x350
       do_writepages+0x32e/0x550
       file_write_and_wait_range+0x23e/0x340
       generic_buffers_fsync_noflush+0x6c/0x180
       ext4_sync_file+0x332/0xb20
       ext4_buffered_write_iter+0x2ca/0x3a0
       ext4_file_write_iter+0x298/0x1bc0
       do_iter_readv_writev+0x623/0x8c0
       vfs_writev+0x31a/0x960
       __se_sys_pwritev2+0x179/0x290
       do_syscall_64+0xfa/0xfa0
       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 ***

2 locks held by syz.4.1550/10209:
 #0: ffff888107770420 (sb_writers#4){.+.+}-{0:0}, at: vfs_writev+0x288/0x960
 #1: ffff888107772b98 (&sbi->s_writepages_rwsem){++++}-{0:0}, at: ext4_writepages+0x1cc/0x350

stack backtrace:
CPU: 0 UID: 0 PID: 10209 Comm: syz.4.1550 Not tainted syzkaller #0 PREEMPT(full) 
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+0x189/0x250
 print_circular_bug+0x2ee/0x310
 check_noncircular+0x134/0x160
 validate_chain+0xb9b/0x2140
 __lock_acquire+0xab9/0xd20
 lock_acquire+0x120/0x360
 down_write+0x96/0x1f0
 ext4_destroy_inline_data+0x28/0xe0
 ext4_do_writepages+0x526/0x4610
 ext4_writepages+0x205/0x350
 do_writepages+0x32e/0x550
 file_write_and_wait_range+0x23e/0x340
 generic_buffers_fsync_noflush+0x6c/0x180
 ext4_sync_file+0x332/0xb20
 ext4_buffered_write_iter+0x2ca/0x3a0
 ext4_file_write_iter+0x298/0x1bc0
 do_iter_readv_writev+0x623/0x8c0
 vfs_writev+0x31a/0x960
 __se_sys_pwritev2+0x179/0x290
 do_syscall_64+0xfa/0xfa0
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7facd918f749
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007facda068038 EFLAGS: 00000246 ORIG_RAX: 0000000000000148
RAX: ffffffffffffffda RBX: 00007facd93e5fa0 RCX: 00007facd918f749
RDX: 0000000000000001 RSI: 00002000000001c0 RDI: 0000000000000004
RBP: 00007facd9213f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000e7b R11: 0000000000000246 R12: 0000000000000000
R13: 00007facd93e6038 R14: 00007facd93e5fa0 R15: 00007ffe2fb11fb8
 </TASK>
EXT4-fs error (device loop4): ext4_mb_generate_buddy:1289: group 0, block bitmap and bg descriptor inconsistent: 25 vs 4278190105 free clusters
EXT4-fs (loop4): Delayed block allocation failed for inode 15 at logical offset 0 with max blocks 1 with error 28
EXT4-fs (loop4): This should not happen!! Data will be lost

EXT4-fs (loop4): Total free blocks count 0
EXT4-fs (loop4): Free/Dirty block details
EXT4-fs (loop4): free_blocks=68451041280
EXT4-fs (loop4): dirty_blocks=80
EXT4-fs (loop4): Block reservation details
EXT4-fs (loop4): i_reserved_data_blocks=5
