====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.2.307/5624 is trying to acquire lock: ffff8880721ca8e8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_write_lock_xattr fs/ext4/xattr.h:158 [inline] ffff8880721ca8e8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_destroy_inline_data+0x24/0xe0 fs/ext4/inline.c:1930 but task is already holding lock: ffff8880767e8c18 (&sbi->s_writepages_rwsem){.+.+}-{0:0}, at: ext4_writepages+0x213/0x2e70 fs/ext4/inode.c:2717 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+0x44/0x1a0 include/linux/percpu-rwsem.h:51 ext4_writepages+0x213/0x2e70 fs/ext4/inode.c:2717 do_writepages+0x3c6/0x640 mm/page-writeback.c:2491 __writeback_single_inode+0x153/0x1170 fs/fs-writeback.c:1622 writeback_single_inode+0x3d2/0x8e0 fs/fs-writeback.c:1743 write_inode_now+0x17f/0x210 fs/fs-writeback.c:2786 iput_final fs/inode.c:1821 [inline] iput+0x643/0x9c0 fs/inode.c:1860 ext4_xattr_block_set+0x2487/0x2fe0 fs/ext4/xattr.c:2148 ext4_xattr_move_to_block fs/ext4/xattr.c:2613 [inline] ext4_xattr_make_inode_space fs/ext4/xattr.c:2688 [inline] ext4_expand_extra_isize_ea+0xfca/0x1d40 fs/ext4/xattr.c:2776 __ext4_expand_extra_isize+0x301/0x3e0 fs/ext4/inode.c:6003 ext4_try_to_expand_extra_isize fs/ext4/inode.c:6046 [inline] __ext4_mark_inode_dirty+0x478/0x760 fs/ext4/inode.c:6124 ext4_evict_inode+0xa67/0x10e0 fs/ext4/inode.c:281 evict+0x4b6/0x8b0 fs/inode.c:705 ext4_orphan_cleanup+0xc32/0x1470 fs/ext4/orphan.c:472 __ext4_fill_super fs/ext4/super.c:5574 [inline] ext4_fill_super+0x6f0c/0x78f0 fs/ext4/super.c:5693 get_tree_bdev+0x3e6/0x610 fs/super.c:1366 vfs_get_tree+0x88/0x270 fs/super.c:1573 do_new_mount+0x247/0xa40 fs/namespace.c:3078 do_mount fs/namespace.c:3421 [inline] __do_sys_mount fs/namespace.c:3629 [inline] __se_sys_mount+0x2e3/0x3d0 fs/namespace.c:3606 do_syscall_x64 arch/x86/entry/common.c:46 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76 entry_SYSCALL_64_after_hwframe+0x68/0xd2 -> #0 (&ei->xattr_sem){++++}-{3:3}: check_prev_add kernel/locking/lockdep.c:3095 [inline] check_prevs_add kernel/locking/lockdep.c:3214 [inline] validate_chain kernel/locking/lockdep.c:3830 [inline] __lock_acquire+0x2d18/0x7c40 kernel/locking/lockdep.c:5063 lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5676 down_write+0x36/0x60 kernel/locking/rwsem.c:1573 ext4_write_lock_xattr fs/ext4/xattr.h:158 [inline] ext4_destroy_inline_data+0x24/0xe0 fs/ext4/inline.c:1930 ext4_writepages+0x599/0x2e70 fs/ext4/inode.c:2763 do_writepages+0x3c6/0x640 mm/page-writeback.c:2491 filemap_fdatawrite_wbc+0x11e/0x180 mm/filemap.c:388 __filemap_fdatawrite_range mm/filemap.c:421 [inline] __filemap_fdatawrite mm/filemap.c:427 [inline] filemap_flush+0xe0/0x140 mm/filemap.c:454 ext4_release_file+0x7e/0x300 fs/ext4/file.c:158 __fput+0x20a/0x8b0 fs/file_table.c:320 task_work_run+0x1d0/0x260 kernel/task_work.c:203 exit_task_work include/linux/task_work.h:39 [inline] do_exit+0x9d5/0x2570 kernel/exit.c:881 do_group_exit+0x229/0x2e0 kernel/exit.c:1024 get_signal+0x1259/0x1340 kernel/signal.c:2872 arch_do_signal_or_restart+0xc4/0x1310 arch/x86/kernel/signal.c:871 exit_to_user_mode_loop+0x70/0x110 kernel/entry/common.c:174 exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:210 irqentry_exit_to_user_mode+0x5/0x30 kernel/entry/common.c:316 exc_page_fault+0x88/0x100 arch/x86/mm/fault.c:1485 asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:608 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&sbi->s_writepages_rwsem); lock(&ei->xattr_sem); lock(&sbi->s_writepages_rwsem); lock(&ei->xattr_sem); *** DEADLOCK *** 1 lock held by syz.2.307/5624: #0: ffff8880767e8c18 (&sbi->s_writepages_rwsem){.+.+}-{0:0}, at: ext4_writepages+0x213/0x2e70 fs/ext4/inode.c:2717 stack backtrace: CPU: 0 PID: 5624 Comm: syz.2.307 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/25/2026 Call Trace: dump_stack_lvl+0x188/0x24e lib/dump_stack.c:106 check_noncircular+0x296/0x330 kernel/locking/lockdep.c:2170 check_prev_add kernel/locking/lockdep.c:3095 [inline] check_prevs_add kernel/locking/lockdep.c:3214 [inline] validate_chain kernel/locking/lockdep.c:3830 [inline] __lock_acquire+0x2d18/0x7c40 kernel/locking/lockdep.c:5063 lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5676 down_write+0x36/0x60 kernel/locking/rwsem.c:1573 ext4_write_lock_xattr fs/ext4/xattr.h:158 [inline] ext4_destroy_inline_data+0x24/0xe0 fs/ext4/inline.c:1930 ext4_writepages+0x599/0x2e70 fs/ext4/inode.c:2763 do_writepages+0x3c6/0x640 mm/page-writeback.c:2491 filemap_fdatawrite_wbc+0x11e/0x180 mm/filemap.c:388 __filemap_fdatawrite_range mm/filemap.c:421 [inline] __filemap_fdatawrite mm/filemap.c:427 [inline] filemap_flush+0xe0/0x140 mm/filemap.c:454 ext4_release_file+0x7e/0x300 fs/ext4/file.c:158 __fput+0x20a/0x8b0 fs/file_table.c:320 task_work_run+0x1d0/0x260 kernel/task_work.c:203 exit_task_work include/linux/task_work.h:39 [inline] do_exit+0x9d5/0x2570 kernel/exit.c:881 do_group_exit+0x229/0x2e0 kernel/exit.c:1024 get_signal+0x1259/0x1340 kernel/signal.c:2872 arch_do_signal_or_restart+0xc4/0x1310 arch/x86/kernel/signal.c:871 exit_to_user_mode_loop+0x70/0x110 kernel/entry/common.c:174 exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:210 irqentry_exit_to_user_mode+0x5/0x30 kernel/entry/common.c:316 exc_page_fault+0x88/0x100 arch/x86/mm/fault.c:1485 asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:608 RIP: 0033:0x7ff5d819dea1 Code: Unable to access opcode bytes at 0x7ff5d819de77. RSP: 002b:fffffffffffffe70 EFLAGS: 00010217 RAX: 0000000000000000 RBX: 00007ff5d8426090 RCX: 00007ff5d819de99 RDX: 0000000000000000 RSI: fffffffffffffe70 RDI: 0000000000008000 RBP: 00007ff5d8233eaf R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000000000 R13: 00007ff5d8426128 R14: 00007ff5d8426090 R15: 00007fff24c40a38 EXT4-fs error (device loop2): ext4_mb_generate_buddy:1126: group 0, block bitmap and bg descriptor inconsistent: 25 vs 150994969 free clusters EXT4-fs (loop2): Delayed block allocation failed for inode 18 at logical offset 0 with max blocks 3 with error 28 EXT4-fs (loop2): This should not happen!! Data will be lost EXT4-fs (loop2): Total free blocks count 0 EXT4-fs (loop2): Free/Dirty block details EXT4-fs (loop2): free_blocks=2415919104 EXT4-fs (loop2): dirty_blocks=38736 EXT4-fs (loop2): Block reservation details EXT4-fs (loop2): i_reserved_data_blocks=2421