====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.2.230/5826 is trying to acquire lock: ffff8880738fc690 (&ei->xattr_sem){++++}-{3:3}, at: ext4_write_lock_xattr fs/ext4/xattr.h:155 [inline] ffff8880738fc690 (&ei->xattr_sem){++++}-{3:3}, at: ext4_destroy_inline_data+0x24/0xe0 fs/ext4/inline.c:1890 but task is already holding lock: ffff88807439cbd8 (&sbi->s_writepages_rwsem){.+.+}-{0:0}, at: ext4_writepages+0x1c0/0x2d20 fs/ext4/inode.c:2689 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+0x46/0x1b0 include/linux/percpu-rwsem.h:51 ext4_writepages+0x1c0/0x2d20 fs/ext4/inode.c:2689 do_writepages+0x48d/0x6d0 mm/page-writeback.c:2386 __writeback_single_inode+0x153/0xda0 fs/fs-writeback.c:1657 writeback_single_inode+0x221/0x8b0 fs/fs-writeback.c:1770 write_inode_now+0x217/0x280 fs/fs-writeback.c:2811 iput_final fs/inode.c:1756 [inline] iput+0x5ab/0x8a0 fs/inode.c:1795 ext4_xattr_set_entry+0x10ff/0x3d30 fs/ext4/xattr.c:1837 ext4_xattr_block_set+0x4f7/0x2d30 fs/ext4/xattr.c:1936 ext4_xattr_move_to_block fs/ext4/xattr.c:2633 [inline] ext4_xattr_make_inode_space fs/ext4/xattr.c:2708 [inline] ext4_expand_extra_isize_ea+0xf4b/0x19a0 fs/ext4/xattr.c:2800 __ext4_expand_extra_isize+0x301/0x3e0 fs/ext4/inode.c:5901 ext4_try_to_expand_extra_isize fs/ext4/inode.c:5944 [inline] __ext4_mark_inode_dirty+0x469/0x700 fs/ext4/inode.c:6022 ext4_evict_inode+0xa81/0x1080 fs/ext4/inode.c:282 evict+0x485/0x870 fs/inode.c:647 ext4_orphan_cleanup+0xaa9/0x12e0 fs/ext4/orphan.c:470 ext4_fill_super+0x92f0/0x9a60 fs/ext4/super.c:4975 mount_bdev+0x287/0x3c0 fs/super.c:1400 legacy_get_tree+0xe6/0x180 fs/fs_context.c:611 vfs_get_tree+0x88/0x270 fs/super.c:1530 do_new_mount+0x24a/0xa40 fs/namespace.c:3034 do_mount fs/namespace.c:3377 [inline] __do_sys_mount fs/namespace.c:3585 [inline] __se_sys_mount+0x2d6/0x3c0 fs/namespace.c:3562 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 -> #0 (&ei->xattr_sem){++++}-{3:3}: check_prev_add kernel/locking/lockdep.c:3053 [inline] check_prevs_add kernel/locking/lockdep.c:3172 [inline] validate_chain kernel/locking/lockdep.c:3788 [inline] __lock_acquire+0x2c33/0x7c60 kernel/locking/lockdep.c:5012 lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623 down_write+0x38/0x60 kernel/locking/rwsem.c:1551 ext4_write_lock_xattr fs/ext4/xattr.h:155 [inline] ext4_destroy_inline_data+0x24/0xe0 fs/ext4/inline.c:1890 ext4_writepages+0x5df/0x2d20 fs/ext4/inode.c:2735 do_writepages+0x48d/0x6d0 mm/page-writeback.c:2386 filemap_fdatawrite_wbc+0x1eb/0x240 mm/filemap.c:400 __filemap_fdatawrite_range mm/filemap.c:433 [inline] __filemap_fdatawrite mm/filemap.c:439 [inline] filemap_flush+0xb3/0x100 mm/filemap.c:466 ext4_release_file+0x7e/0x310 fs/ext4/file.c:141 __fput+0x234/0x930 fs/file_table.c:311 task_work_run+0x125/0x1a0 kernel/task_work.c:188 exit_task_work include/linux/task_work.h:33 [inline] do_exit+0x61e/0x20a0 kernel/exit.c:883 do_group_exit+0x12e/0x300 kernel/exit.c:997 get_signal+0x6ca/0x12c0 kernel/signal.c:2900 arch_do_signal_or_restart+0xc1/0x1300 arch/x86/kernel/signal.c:867 handle_signal_work kernel/entry/common.c:154 [inline] exit_to_user_mode_loop+0x9e/0x130 kernel/entry/common.c:178 exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:214 irqentry_exit_to_user_mode+0x5/0x30 kernel/entry/common.c:320 exc_page_fault+0x88/0x100 arch/x86/mm/fault.c:1504 asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:606 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.230/5826: #0: ffff88807439cbd8 (&sbi->s_writepages_rwsem){.+.+}-{0:0}, at: ext4_writepages+0x1c0/0x2d20 fs/ext4/inode.c:2689 stack backtrace: CPU: 1 PID: 5826 Comm: syz.2.230 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025 Call Trace: dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106 check_noncircular+0x274/0x310 kernel/locking/lockdep.c:2133 check_prev_add kernel/locking/lockdep.c:3053 [inline] check_prevs_add kernel/locking/lockdep.c:3172 [inline] validate_chain kernel/locking/lockdep.c:3788 [inline] __lock_acquire+0x2c33/0x7c60 kernel/locking/lockdep.c:5012 lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623 down_write+0x38/0x60 kernel/locking/rwsem.c:1551 ext4_write_lock_xattr fs/ext4/xattr.h:155 [inline] ext4_destroy_inline_data+0x24/0xe0 fs/ext4/inline.c:1890 ext4_writepages+0x5df/0x2d20 fs/ext4/inode.c:2735 do_writepages+0x48d/0x6d0 mm/page-writeback.c:2386 filemap_fdatawrite_wbc+0x1eb/0x240 mm/filemap.c:400 __filemap_fdatawrite_range mm/filemap.c:433 [inline] __filemap_fdatawrite mm/filemap.c:439 [inline] filemap_flush+0xb3/0x100 mm/filemap.c:466 ext4_release_file+0x7e/0x310 fs/ext4/file.c:141 __fput+0x234/0x930 fs/file_table.c:311 task_work_run+0x125/0x1a0 kernel/task_work.c:188 exit_task_work include/linux/task_work.h:33 [inline] do_exit+0x61e/0x20a0 kernel/exit.c:883 do_group_exit+0x12e/0x300 kernel/exit.c:997 get_signal+0x6ca/0x12c0 kernel/signal.c:2900 arch_do_signal_or_restart+0xc1/0x1300 arch/x86/kernel/signal.c:867 handle_signal_work kernel/entry/common.c:154 [inline] exit_to_user_mode_loop+0x9e/0x130 kernel/entry/common.c:178 exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:214 irqentry_exit_to_user_mode+0x5/0x30 kernel/entry/common.c:320 exc_page_fault+0x88/0x100 arch/x86/mm/fault.c:1504 asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:606 RIP: 0033:0x7fa40bd04751 Code: Unable to access opcode bytes at RIP 0x7fa40bd04727. RSP: 002b:fffffffffffffe70 EFLAGS: 00010217 RAX: 0000000000000000 RBX: 00007fa40bf5afa0 RCX: 00007fa40bd04749 RDX: 0000000000000000 RSI: fffffffffffffe70 RDI: 0000000000008000 RBP: 00007fa40bd88f91 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000000000 R13: 00007fa40bf5b038 R14: 00007fa40bf5afa0 R15: 00007fff969f81f8 EXT4-fs error (device loop2): ext4_validate_block_bitmap:429: comm syz.2.230: bg 0: block 5: invalid block bitmap EXT4-fs (loop2): Delayed block allocation failed for inode 18 at logical offset 0 with max blocks 5 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=0 EXT4-fs (loop2): dirty_blocks=3201 EXT4-fs (loop2): Block reservation details EXT4-fs (loop2): i_reserved_data_blocks=3201