======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.2.11194/16094 is trying to acquire lock:
ffff8881ba1aab98 (&sbi->s_writepages_rwsem){++++}-{0:0}, at: ext4_writepages+0x1cc/0x350

but task is already holding lock:
ffff8881bf11e9f8 (&ei->xattr_sem){++++}-{4:4}, at: __ext4_mark_inode_dirty+0x3eb/0x700

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&ei->xattr_sem){++++}-{4:4}:
       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
       __writeback_single_inode+0x145/0xff0
       writeback_sb_inodes+0x6c7/0x1010
       wb_writeback+0x43b/0xaf0
       wb_workfn+0x409/0xef0
       process_scheduled_works+0xae1/0x17b0
       worker_thread+0x8a0/0xda0
       kthread+0x711/0x8a0
       ret_from_fork+0x4bc/0x870
       ret_from_fork_asm+0x1a/0x30

-> #0 (&sbi->s_writepages_rwsem){++++}-{0:0}:
       validate_chain+0xb9b/0x2140
       __lock_acquire+0xab9/0xd20
       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

other info that might help us debug this:

 Possible unsafe locking scenario:

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

 *** DEADLOCK ***

3 locks held by syz.2.11194/16094:
 #0: ffff8881ba1a80e0 (&type->s_umount_key#27/1){+.+.}-{4:4}, at: alloc_super+0x1bb/0x930
 #1: ffff8881ba1a8610 (sb_internal){++++}-{0:0}, at: ext4_evict_inode+0x2d6/0xee0
 #2: ffff8881bf11e9f8 (&ei->xattr_sem){++++}-{4:4}, at: __ext4_mark_inode_dirty+0x3eb/0x700

stack backtrace:
CPU: 1 UID: 0 PID: 16094 Comm: syz.2.11194 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
 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
RIP: 0033:0x7f5048f90eea
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 1a 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 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:00007f5049eeae68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f5049eeaef0 RCX: 00007f5048f90eea
RDX: 0000200000000180 RSI: 0000200000000080 RDI: 00007f5049eeaeb0
RBP: 0000200000000180 R08: 00007f5049eeaef0 R09: 0000000000800700
R10: 0000000000800700 R11: 0000000000000246 R12: 0000200000000080
R13: 00007f5049eeaeb0 R14: 000000000000046f R15: 00002000000000c0
 </TASK>
EXT4-fs error (device loop2): ext4_xattr_inode_iget:441: inode #11: comm syz.2.11194: iget: bad extra_isize 90 (inode size 256)
EXT4-fs error (device loop2): ext4_xattr_inode_iget:446: comm syz.2.11194: error while reading EA inode 11 err=-117
EXT4-fs error (device loop2): ext4_xattr_inode_iget:441: inode #11: comm syz.2.11194: iget: bad extra_isize 90 (inode size 256)
EXT4-fs error (device loop2): ext4_xattr_inode_iget:446: comm syz.2.11194: error while reading EA inode 11 err=-117
EXT4-fs error (device loop2): ext4_xattr_inode_iget:441: inode #18: comm syz.2.11194: iget: bad extra_isize 90 (inode size 256)
EXT4-fs error (device loop2): ext4_xattr_inode_iget:446: comm syz.2.11194: error while reading EA inode 18 err=-117
EXT4-fs error (device loop2): ext4_xattr_inode_iget:441: inode #18: comm syz.2.11194: iget: bad extra_isize 90 (inode size 256)
EXT4-fs error (device loop2): ext4_xattr_inode_iget:446: comm syz.2.11194: error while reading EA inode 18 err=-117
EXT4-fs (loop2): 1 orphan inode deleted
EXT4-fs (loop2): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: none.
