====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.0.36/4405 is trying to acquire lock: ffff88805e7714b8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_write_lock_xattr fs/ext4/xattr.h:158 [inline] ffff88805e7714b8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_destroy_inline_data+0x24/0xe0 fs/ext4/inline.c:1908 but task is already holding lock: ffff88801fc88c58 (&sbi->s_writepages_rwsem){.+.+}-{0:0}, at: ext4_writepages+0x213/0x2d40 fs/ext4/inode.c:2691 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+0x213/0x2d40 fs/ext4/inode.c:2691 do_writepages+0x493/0x700 mm/page-writeback.c:2386 __writeback_single_inode+0x153/0xda0 fs/fs-writeback.c:1657 writeback_single_inode+0x3d2/0x8e0 fs/fs-writeback.c:1770 write_inode_now+0x23b/0x2c0 fs/fs-writeback.c:2817 iput_final fs/inode.c:1756 [inline] iput+0x599/0x880 fs/inode.c:1795 ext4_xattr_set_entry+0x1d76/0x3f70 fs/ext4/xattr.c:1827 ext4_xattr_block_set+0x8a7/0x2d00 fs/ext4/xattr.c:1995 ext4_xattr_move_to_block fs/ext4/xattr.c:2622 [inline] ext4_xattr_make_inode_space fs/ext4/xattr.c:2697 [inline] ext4_expand_extra_isize_ea+0xfdc/0x18c0 fs/ext4/xattr.c:2785 __ext4_expand_extra_isize+0x301/0x3e0 fs/ext4/inode.c:5924 ext4_try_to_expand_extra_isize fs/ext4/inode.c:5967 [inline] __ext4_mark_inode_dirty+0x444/0x6c0 fs/ext4/inode.c:6045 ext4_evict_inode+0xa55/0x1050 fs/ext4/inode.c:284 evict+0x4b6/0x8b0 fs/inode.c:647 ext4_orphan_cleanup+0xad8/0x1320 fs/ext4/orphan.c:472 ext4_fill_super+0x8c65/0x93f0 fs/ext4/super.c:5006 mount_bdev+0x28a/0x3c0 fs/super.c:1411 legacy_get_tree+0xe6/0x180 fs/fs_context.c:611 vfs_get_tree+0x88/0x270 fs/super.c:1541 do_new_mount+0x247/0xa40 fs/namespace.c:3034 do_mount fs/namespace.c:3377 [inline] __do_sys_mount fs/namespace.c:3585 [inline] __se_sys_mount+0x2e3/0x3d0 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+0x2c66/0x7b50 kernel/locking/lockdep.c:5012 lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623 down_write+0x38/0x60 kernel/locking/rwsem.c:1551 ext4_write_lock_xattr fs/ext4/xattr.h:158 [inline] ext4_destroy_inline_data+0x24/0xe0 fs/ext4/inline.c:1908 ext4_writepages+0x599/0x2d40 fs/ext4/inode.c:2737 do_writepages+0x493/0x700 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+0xd4/0x130 mm/filemap.c:466 ext4_convert_inline_data+0x186/0x5b0 fs/ext4/inline.c:2084 ext4_page_mkwrite+0x1df/0x1250 fs/ext4/inode.c:6199 do_page_mkwrite+0x168/0x3c0 mm/memory.c:2922 wp_page_shared+0x163/0x6c0 mm/memory.c:3259 handle_pte_fault mm/memory.c:4668 [inline] __handle_mm_fault mm/memory.c:4785 [inline] handle_mm_fault+0x1fbd/0x4440 mm/memory.c:4883 do_user_addr_fault+0x494/0xc90 arch/x86/mm/fault.c:1355 handle_page_fault arch/x86/mm/fault.c:1443 [inline] exc_page_fault+0x60/0x100 arch/x86/mm/fault.c:1496 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 *** 4 locks held by syz.0.36/4405: #0: ffff88801ecb2b28 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_trylock include/linux/mmap_lock.h:136 [inline] #0: ffff88801ecb2b28 (&mm->mmap_lock){++++}-{3:3}, at: do_user_addr_fault+0x2bb/0xc90 arch/x86/mm/fault.c:1296 #1: ffff888023084558 (sb_pagefaults){.+.+}-{0:0}, at: __sb_start_write include/linux/fs.h:1817 [inline] #1: ffff888023084558 (sb_pagefaults){.+.+}-{0:0}, at: sb_start_pagefault include/linux/fs.h:1916 [inline] #1: ffff888023084558 (sb_pagefaults){.+.+}-{0:0}, at: ext4_page_mkwrite+0x1a5/0x1250 fs/ext4/inode.c:6194 #2: ffff88805e771980 (mapping.invalidate_lock){++++}-{3:3}, at: filemap_invalidate_lock_shared include/linux/fs.h:848 [inline] #2: ffff88805e771980 (mapping.invalidate_lock){++++}-{3:3}, at: ext4_page_mkwrite+0x1d2/0x1250 fs/ext4/inode.c:6197 #3: ffff88801fc88c58 (&sbi->s_writepages_rwsem){.+.+}-{0:0}, at: ext4_writepages+0x213/0x2d40 fs/ext4/inode.c:2691 stack backtrace: CPU: 1 PID: 4405 Comm: syz.0.36 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026 Call Trace: dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106 check_noncircular+0x296/0x330 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+0x2c66/0x7b50 kernel/locking/lockdep.c:5012 lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623 down_write+0x38/0x60 kernel/locking/rwsem.c:1551 ext4_write_lock_xattr fs/ext4/xattr.h:158 [inline] ext4_destroy_inline_data+0x24/0xe0 fs/ext4/inline.c:1908 ext4_writepages+0x599/0x2d40 fs/ext4/inode.c:2737 do_writepages+0x493/0x700 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+0xd4/0x130 mm/filemap.c:466 ext4_convert_inline_data+0x186/0x5b0 fs/ext4/inline.c:2084 ext4_page_mkwrite+0x1df/0x1250 fs/ext4/inode.c:6199 do_page_mkwrite+0x168/0x3c0 mm/memory.c:2922 wp_page_shared+0x163/0x6c0 mm/memory.c:3259 handle_pte_fault mm/memory.c:4668 [inline] __handle_mm_fault mm/memory.c:4785 [inline] handle_mm_fault+0x1fbd/0x4440 mm/memory.c:4883 do_user_addr_fault+0x494/0xc90 arch/x86/mm/fault.c:1355 handle_page_fault arch/x86/mm/fault.c:1443 [inline] exc_page_fault+0x60/0x100 arch/x86/mm/fault.c:1496 asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:606 RIP: 0033:0x7f11d67c0528 Code: 25 00 00 00 00 48 8d b8 d8 fe ff ff 4c 89 74 24 50 e8 ac 3c 0d 00 85 c0 75 13 48 8b 84 24 80 00 00 00 48 8b b4 24 c0 00 00 00 <48> 89 30 64 f0 83 2c 25 a0 ff ff ff 01 4c 8b 74 24 50 e9 61 f5 ff RSP: 002b:00007ffc9e365a40 EFLAGS: 00010246 RAX: 00002000000000c0 RBX: 0000000000000002 RCX: 0000000000000007 RDX: b595cd44588b75dd RSI: 0000200000000080 RDI: 00005555900743d8 RBP: fffffffffffffffe R08: 0000001b31520000 R09: 0000000000000002 R10: 0000000000000080 R11: 0000000000000001 R12: 00007ffc9e365b60 R13: 00007f11d6b7afac R14: 0000000000011ccc R15: 00007f11d6b7afa0 EXT4-fs error (device loop0): ext4_mb_generate_buddy:1176: group 0, block bitmap and bg descriptor inconsistent: 25 vs 281 free clusters EXT4-fs (loop0): Delayed block allocation failed for inode 15 at logical offset 0 with max blocks 1 with error 28 EXT4-fs (loop0): This should not happen!! Data will be lost EXT4-fs (loop0): Total free blocks count 0 EXT4-fs (loop0): Free/Dirty block details EXT4-fs (loop0): free_blocks=4096 EXT4-fs (loop0): dirty_blocks=64 EXT4-fs (loop0): Block reservation details EXT4-fs (loop0): i_reserved_data_blocks=4 EXT4-fs (loop0): Delayed block allocation failed for inode 15 at logical offset 31 with max blocks 33 with error 28 EXT4-fs (loop0): This should not happen!! Data will be lost