EXT4-fs: Ignoring removed nobh option
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.4.1234/11943 is trying to acquire lock:
ffff88801e188b98 (&sbi->s_writepages_rwsem){++++}-{0:0}, at: ext4_writepages+0x205/0x3b0

but task is already holding lock:
ffff8881bbee6aa8 (&ei->xattr_sem){++++}-{4:4}, at: __ext4_mark_inode_dirty+0x3db/0x6e0

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&ei->xattr_sem){++++}-{4:4}:
       down_write+0x96/0x200
       ext4_destroy_inline_data+0x28/0xe0
       ext4_do_writepages+0x51e/0x4600
       ext4_writepages+0x241/0x3b0
       do_writepages+0x32e/0x550
       file_write_and_wait_range+0x36e/0x440
       generic_buffers_fsync_noflush+0x70/0x1d0
       ext4_sync_file+0x321/0xad0
       ext4_buffered_write_iter+0x2ca/0x3a0
       ext4_file_write_iter+0x298/0x1c10
       vfs_write+0x61d/0xb90
       __x64_sys_pwrite64+0x199/0x230
       do_syscall_64+0xe2/0xf80
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&sbi->s_writepages_rwsem){++++}-{0:0}:
       __lock_acquire+0x15a5/0x2cf0
       lock_acquire+0x106/0x330
       percpu_down_read_internal+0x48/0x1c0
       ext4_writepages+0x205/0x3b0
       do_writepages+0x32e/0x550
       __writeback_single_inode+0x133/0x1230
       writeback_single_inode+0x493/0xc70
       write_inode_now+0x1c2/0x290
       iput+0xa73/0x1020
       ext4_xattr_block_set+0x1fd4/0x2ad0
       ext4_expand_extra_isize_ea+0x12cf/0x1ea0
       __ext4_expand_extra_isize+0x30d/0x400
       __ext4_mark_inode_dirty+0x45c/0x6e0
       ext4_evict_inode+0x7a1/0xe60
       evict+0x61e/0xb10
       ext4_orphan_cleanup+0xc38/0x1470
       ext4_fill_super+0x5932/0x61f0
       get_tree_bdev_flags+0x431/0x4f0
       vfs_get_tree+0x92/0x2a0
       do_new_mount+0x329/0xa50
       __se_sys_mount+0x31d/0x420
       do_syscall_64+0xe2/0xf80
       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.4.1234/11943:
 #0: ffff88801e18c0e0 (&type->s_umount_key#27/1){+.+.}-{4:4}, at: alloc_super+0x28c/0xaa0
 #1: ffff88801e18c610 (sb_internal){++++}-{0:0}, at: ext4_evict_inode+0x274/0xe60
 #2: ffff8881bbee6aa8 (&ei->xattr_sem){++++}-{4:4}, at: __ext4_mark_inode_dirty+0x3db/0x6e0

stack backtrace:
CPU: 1 UID: 0 PID: 11943 Comm: syz.4.1234 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+0xe8/0x150
 print_circular_bug+0x2e1/0x300
 check_noncircular+0x12e/0x150
 __lock_acquire+0x15a5/0x2cf0
 lock_acquire+0x106/0x330
 percpu_down_read_internal+0x48/0x1c0
 ext4_writepages+0x205/0x3b0
 do_writepages+0x32e/0x550
 __writeback_single_inode+0x133/0x1230
 writeback_single_inode+0x493/0xc70
 write_inode_now+0x1c2/0x290
 iput+0xa73/0x1020
 ext4_xattr_block_set+0x1fd4/0x2ad0
 ext4_expand_extra_isize_ea+0x12cf/0x1ea0
 __ext4_expand_extra_isize+0x30d/0x400
 __ext4_mark_inode_dirty+0x45c/0x6e0
 ext4_evict_inode+0x7a1/0xe60
 evict+0x61e/0xb10
 ext4_orphan_cleanup+0xc38/0x1470
 ext4_fill_super+0x5932/0x61f0
 get_tree_bdev_flags+0x431/0x4f0
 vfs_get_tree+0x92/0x2a0
 do_new_mount+0x329/0xa50
 __se_sys_mount+0x31d/0x420
 do_syscall_64+0xe2/0xf80
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fb2d139bf4a
Code: 48 c7 c2 e8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff c3 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fb2d2202e58 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fb2d2202ee0 RCX: 00007fb2d139bf4a
RDX: 0000200000000180 RSI: 0000200000000080 RDI: 00007fb2d2202ea0
RBP: 0000200000000180 R08: 00007fb2d2202ee0 R09: 0000000000800700
R10: 0000000000800700 R11: 0000000000000246 R12: 0000200000000080
R13: 00007fb2d2202ea0 R14: 000000000000046f R15: 00002000000001c0
 </TASK>
EXT4-fs error (device loop4): ext4_xattr_inode_iget:441: inode #11: comm syz.4.1234: iget: bad extra_isize 90 (inode size 256)
EXT4-fs error (device loop4): ext4_xattr_inode_iget:446: comm syz.4.1234: error while reading EA inode 11 err=-117
EXT4-fs error (device loop4): ext4_xattr_inode_iget:441: inode #11: comm syz.4.1234: iget: bad extra_isize 90 (inode size 256)
EXT4-fs error (device loop4): ext4_xattr_inode_iget:446: comm syz.4.1234: error while reading EA inode 11 err=-117
EXT4-fs error (device loop4): ext4_xattr_inode_iget:441: inode #18: comm syz.4.1234: iget: bad extra_isize 90 (inode size 256)
EXT4-fs error (device loop4): ext4_xattr_inode_iget:446: comm syz.4.1234: error while reading EA inode 18 err=-117
EXT4-fs error (device loop4): ext4_xattr_inode_iget:441: inode #18: comm syz.4.1234: iget: bad extra_isize 90 (inode size 256)
EXT4-fs error (device loop4): ext4_xattr_inode_iget:446: comm syz.4.1234: error while reading EA inode 18 err=-117
EXT4-fs (loop4): 1 orphan inode deleted
EXT4-fs (loop4): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: writeback.
EXT4-fs (loop4): unmounting filesystem 00000000-0000-0000-0000-000000000000.
