EXT4-fs (loop5): 2 truncates cleaned up
EXT4-fs (loop5): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: writeback.
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Tainted: G             L     
------------------------------------------------------
syz.5.1240/12131 is trying to acquire lock:
ffff8881aa4b00c8 (&ei->xattr_sem){++++}-{4:4}, at: ext4_destroy_inline_data+0x28/0xe0

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

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+0x1ca/0x350
       do_writepages+0x32e/0x550
       __writeback_single_inode+0x133/0x1240
       writeback_single_inode+0x493/0xc70
       write_inode_now+0x160/0x1d0
       iput+0xa77/0x1030
       ext4_xattr_block_set+0x1fce/0x2ac0
       ext4_expand_extra_isize_ea+0x12da/0x1ea0
       __ext4_expand_extra_isize+0x30d/0x400
       __ext4_mark_inode_dirty+0x45c/0x6e0
       ext4_evict_inode+0x79c/0xe60
       evict+0x5f4/0xae0
       ext4_orphan_cleanup+0xc20/0x1460
       ext4_fill_super+0x58a1/0x6160
       get_tree_bdev_flags+0x40e/0x4d0
       vfs_get_tree+0x92/0x2a0
       do_new_mount+0x302/0xa10
       __se_sys_mount+0x313/0x410
       do_syscall_64+0xfa/0xf80
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&ei->xattr_sem){++++}-{4:4}:
       __lock_acquire+0x15a6/0x2cf0
       lock_acquire+0x117/0x340
       down_write+0x96/0x1f0
       ext4_destroy_inline_data+0x28/0xe0
       ext4_do_writepages+0x4e6/0x4500
       ext4_writepages+0x203/0x350
       do_writepages+0x32e/0x550
       filemap_flush+0x191/0x230
       ext4_rename2+0xeab/0x2f50
       vfs_rename+0xbb6/0xee0
       do_renameat2+0x538/0x8e0
       __x64_sys_rename+0x82/0x90
       do_syscall_64+0xfa/0xf80
       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 ***

5 locks held by syz.5.1240/12131:
 #0: ffff888105738420 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90
 #1: ffff888119c8b400 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: __start_renaming+0x148/0x410
 #2: ffff8881aa4b03e0 (&sb->s_type->i_mutex_key#11){++++}-{4:4}, at: lock_two_nondirectories+0xe7/0x180
 #3: ffff8881aa4b0d80 (&sb->s_type->i_mutex_key#11/4){+.+.}-{4:4}, at: vfs_rename+0x661/0xee0
 #4: ffff88811188eb98 (&sbi->s_writepages_rwsem){++++}-{0:0}, at: ext4_writepages+0x1ca/0x350

stack backtrace:
CPU: 1 UID: 0 PID: 12131 Comm: syz.5.1240 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+0x189/0x250
 print_circular_bug+0x2e2/0x300
 check_noncircular+0x12e/0x150
 __lock_acquire+0x15a6/0x2cf0
 lock_acquire+0x117/0x340
 down_write+0x96/0x1f0
 ext4_destroy_inline_data+0x28/0xe0
 ext4_do_writepages+0x4e6/0x4500
 ext4_writepages+0x203/0x350
 do_writepages+0x32e/0x550
 filemap_flush+0x191/0x230
 ext4_rename2+0xeab/0x2f50
 vfs_rename+0xbb6/0xee0
 do_renameat2+0x538/0x8e0
 __x64_sys_rename+0x82/0x90
 do_syscall_64+0xfa/0xf80
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fbd1858f7c9
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:00007fbd193da038 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007fbd187e5fa0 RCX: 00007fbd1858f7c9
RDX: 0000000000000000 RSI: 0000200000000100 RDI: 0000200000000000
RBP: 00007fbd185f297f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fbd187e6038 R14: 00007fbd187e5fa0 R15: 00007fff2bba0118
 </TASK>
EXT4-fs error (device loop5): ext4_validate_block_bitmap:432: comm syz.5.1240: bg 0: block 5: invalid block bitmap
EXT4-fs (loop5): Delayed block allocation failed for inode 15 at logical offset 0 with max blocks 1 with error 28
EXT4-fs (loop5): This should not happen!! Data will be lost

EXT4-fs (loop5): Total free blocks count 0
EXT4-fs (loop5): Free/Dirty block details
EXT4-fs (loop5): free_blocks=0
EXT4-fs (loop5): dirty_blocks=2
EXT4-fs (loop5): Block reservation details
EXT4-fs (loop5): i_reserved_data_blocks=2
