EXT4-fs (loop1): 1 truncate cleaned up EXT4-fs (loop1): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: none. ====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.1.3857/22138 is trying to acquire lock: ffff88805e4d5ac8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_write_lock_xattr fs/ext4/xattr.h:158 [inline] ffff88805e4d5ac8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_destroy_inline_data+0x28/0xe0 fs/ext4/inline.c:1902 but task is already holding lock: ffff88806430ac58 (&sbi->s_writepages_rwsem){++++}-{0:0}, at: ext4_writepages_down_read fs/ext4/ext4.h:1768 [inline] ffff88806430ac58 (&sbi->s_writepages_rwsem){++++}-{0:0}, at: ext4_writepages+0x1a4/0x350 fs/ext4/inode.c:2808 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_down_read fs/ext4/ext4.h:1768 [inline] ext4_writepages+0x1a4/0x350 fs/ext4/inode.c:2808 do_writepages+0x351/0x590 mm/page-writeback.c:2575 __writeback_single_inode+0x14e/0xee0 fs/fs-writeback.c:1635 writeback_single_inode+0x21f/0x760 fs/fs-writeback.c:1756 write_inode_now+0x183/0x210 fs/fs-writeback.c:2808 iput_final fs/inode.c:1807 [inline] iput+0x58f/0x900 fs/inode.c:1846 ext4_xattr_block_set+0x2228/0x2fe0 fs/ext4/xattr.c:2148 ext4_xattr_move_to_block fs/ext4/xattr.c:2666 [inline] ext4_xattr_make_inode_space fs/ext4/xattr.c:2741 [inline] ext4_expand_extra_isize_ea+0x128f/0x1e70 fs/ext4/xattr.c:2829 __ext4_expand_extra_isize+0x306/0x400 fs/ext4/inode.c:5990 ext4_try_to_expand_extra_isize fs/ext4/inode.c:6033 [inline] __ext4_mark_inode_dirty+0x458/0x6d0 fs/ext4/inode.c:6111 ext4_evict_inode+0x7dd/0xe70 fs/ext4/inode.c:254 evict+0x4b7/0x8a0 fs/inode.c:705 ext4_orphan_cleanup+0xc33/0x1470 fs/ext4/orphan.c:472 __ext4_fill_super fs/ext4/super.c:5621 [inline] ext4_fill_super+0x5fb5/0x6870 fs/ext4/super.c:5744 get_tree_bdev+0x3e5/0x520 fs/super.c:1591 vfs_get_tree+0x8c/0x280 fs/super.c:1764 do_new_mount+0x24a/0xa40 fs/namespace.c:3386 do_mount fs/namespace.c:3726 [inline] __do_sys_mount fs/namespace.c:3935 [inline] __se_sys_mount+0x2e7/0x3d0 fs/namespace.c:3912 do_syscall_x64 arch/x86/entry/common.c:46 [inline] do_syscall_64+0x55/0xb0 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:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain kernel/locking/lockdep.c:3869 [inline] __lock_acquire+0x37ef/0x7d80 kernel/locking/lockdep.c:5137 lock_acquire+0x19e/0x420 kernel/locking/lockdep.c:5754 down_write+0x97/0x200 kernel/locking/rwsem.c:1573 ext4_write_lock_xattr fs/ext4/xattr.h:158 [inline] ext4_destroy_inline_data+0x28/0xe0 fs/ext4/inline.c:1902 ext4_do_writepages+0x4f2/0x3990 fs/ext4/inode.c:2606 ext4_writepages+0x1dd/0x350 fs/ext4/inode.c:2809 do_writepages+0x351/0x590 mm/page-writeback.c:2575 filemap_fdatawrite_wbc+0x122/0x180 mm/filemap.c:390 __filemap_fdatawrite_range mm/filemap.c:423 [inline] file_write_and_wait_range+0x197/0x280 mm/filemap.c:781 generic_buffers_fsync_noflush+0x6f/0x160 fs/buffer.c:609 ext4_fsync_nojournal fs/ext4/fsync.c:92 [inline] ext4_sync_file+0x460/0xd50 fs/ext4/fsync.c:163 generic_write_sync include/linux/fs.h:2664 [inline] ext4_buffered_write_iter+0x2c0/0x350 fs/ext4/file.c:305 ext4_file_write_iter+0x1e7/0x1980 fs/ext4/file.c:-1 call_write_iter include/linux/fs.h:2018 [inline] new_sync_write fs/read_write.c:491 [inline] vfs_write+0x474/0x9a0 fs/read_write.c:584 ksys_pwrite64 fs/read_write.c:699 [inline] __do_sys_pwrite64 fs/read_write.c:709 [inline] __se_sys_pwrite64 fs/read_write.c:706 [inline] __x64_sys_pwrite64+0x198/0x220 fs/read_write.c:706 do_syscall_x64 arch/x86/entry/common.c:46 [inline] do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:76 entry_SYSCALL_64_after_hwframe+0x68/0xd2 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 *** 2 locks held by syz.1.3857/22138: #0: ffff888064308418 (sb_writers#4){.+.+}-{0:0}, at: vfs_write+0x21e/0x9a0 fs/read_write.c:580 #1: ffff88806430ac58 (&sbi->s_writepages_rwsem){++++}-{0:0}, at: ext4_writepages_down_read fs/ext4/ext4.h:1768 [inline] #1: ffff88806430ac58 (&sbi->s_writepages_rwsem){++++}-{0:0}, at: ext4_writepages+0x1a4/0x350 fs/ext4/inode.c:2808 stack backtrace: CPU: 1 PID: 22138 Comm: syz.1.3857 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/2026 Call Trace: dump_stack_lvl+0x18c/0x250 lib/dump_stack.c:106 check_noncircular+0x2fc/0x400 kernel/locking/lockdep.c:2187 check_prev_add kernel/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain kernel/locking/lockdep.c:3869 [inline] __lock_acquire+0x37ef/0x7d80 kernel/locking/lockdep.c:5137 lock_acquire+0x19e/0x420 kernel/locking/lockdep.c:5754 down_write+0x97/0x200 kernel/locking/rwsem.c:1573 ext4_write_lock_xattr fs/ext4/xattr.h:158 [inline] ext4_destroy_inline_data+0x28/0xe0 fs/ext4/inline.c:1902 ext4_do_writepages+0x4f2/0x3990 fs/ext4/inode.c:2606 ext4_writepages+0x1dd/0x350 fs/ext4/inode.c:2809 do_writepages+0x351/0x590 mm/page-writeback.c:2575 filemap_fdatawrite_wbc+0x122/0x180 mm/filemap.c:390 __filemap_fdatawrite_range mm/filemap.c:423 [inline] file_write_and_wait_range+0x197/0x280 mm/filemap.c:781 generic_buffers_fsync_noflush+0x6f/0x160 fs/buffer.c:609 ext4_fsync_nojournal fs/ext4/fsync.c:92 [inline] ext4_sync_file+0x460/0xd50 fs/ext4/fsync.c:163 generic_write_sync include/linux/fs.h:2664 [inline] ext4_buffered_write_iter+0x2c0/0x350 fs/ext4/file.c:305 ext4_file_write_iter+0x1e7/0x1980 fs/ext4/file.c:-1 call_write_iter include/linux/fs.h:2018 [inline] new_sync_write fs/read_write.c:491 [inline] vfs_write+0x474/0x9a0 fs/read_write.c:584 ksys_pwrite64 fs/read_write.c:699 [inline] __do_sys_pwrite64 fs/read_write.c:709 [inline] __se_sys_pwrite64 fs/read_write.c:706 [inline] __x64_sys_pwrite64+0x198/0x220 fs/read_write.c:706 do_syscall_x64 arch/x86/entry/common.c:46 [inline] do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:76 entry_SYSCALL_64_after_hwframe+0x68/0xd2 RIP: 0033:0x7f40dc59de59 Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f40dd501028 EFLAGS: 00000246 ORIG_RAX: 0000000000000012 RAX: ffffffffffffffda RBX: 00007f40dc825fa0 RCX: 00007f40dc59de59 RDX: 000000000000fdef RSI: 0000200000000140 RDI: 0000000000000004 RBP: 00007f40dc633e6f R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000e7c R11: 0000000000000246 R12: 0000000000000000 R13: 00007f40dc826038 R14: 00007f40dc825fa0 R15: 00007ffe7183fcb8 EXT4-fs error (device loop1): ext4_validate_block_bitmap:439: comm syz.1.3857: bg 0: block 465: padding at end of block bitmap is not set EXT4-fs (loop1): Remounting filesystem read-only