====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ kworker/u4:16/6249 is trying to acquire lock: ffff0000cf7dc700 (&ei->xattr_sem){++++}-{3:3}, at: ext4_write_lock_xattr fs/ext4/xattr.h:158 [inline] ffff0000cf7dc700 (&ei->xattr_sem){++++}-{3:3}, at: ext4_destroy_inline_data+0x30/0x114 fs/ext4/inline.c:1922 but task is already holding lock: ffff00010c174c18 (&sbi->s_writepages_rwsem){.+.+}-{0:0}, at: ext4_writepages+0x1b0/0x28fc 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+0x70/0x2a8 include/linux/percpu-rwsem.h:51 ext4_writepages+0x1b0/0x28fc fs/ext4/inode.c:2717 do_writepages+0x2c4/0x50c mm/page-writeback.c:2491 __writeback_single_inode+0x164/0x157c fs/fs-writeback.c:1622 writeback_single_inode+0x1cc/0x73c fs/fs-writeback.c:1743 write_inode_now+0x150/0x1cc fs/fs-writeback.c:2786 iput_final fs/inode.c:1821 [inline] iput+0x5b8/0x7e8 fs/inode.c:1860 ext4_xattr_block_set+0x1eb0/0x28b4 fs/ext4/xattr.c:2095 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+0xea4/0x1818 fs/ext4/xattr.c:2776 __ext4_expand_extra_isize+0x2a0/0x364 fs/ext4/inode.c:6003 ext4_try_to_expand_extra_isize fs/ext4/inode.c:6046 [inline] __ext4_mark_inode_dirty+0x3d4/0x7b4 fs/ext4/inode.c:6124 ext4_evict_inode+0xb50/0x1264 fs/ext4/inode.c:281 evict+0x3d8/0x824 fs/inode.c:705 iput_final fs/inode.c:1834 [inline] iput+0x728/0x7e8 fs/inode.c:1860 ext4_process_orphan+0x24c/0x2c0 fs/ext4/orphan.c:358 ext4_orphan_cleanup+0x964/0x1090 fs/ext4/orphan.c:472 __ext4_fill_super fs/ext4/super.c:5574 [inline] ext4_fill_super+0x5af8/0x63bc fs/ext4/super.c:5693 get_tree_bdev+0x35c/0x54c fs/super.c:1366 ext4_get_tree+0x28/0x38 fs/ext4/super.c:5723 vfs_get_tree+0x90/0x278 fs/super.c:1573 do_new_mount+0x228/0x804 fs/namespace.c:3078 path_mount+0x5ac/0xe6c fs/namespace.c:3408 do_mount fs/namespace.c:3421 [inline] __do_sys_mount fs/namespace.c:3629 [inline] __se_sys_mount fs/namespace.c:3606 [inline] __arm64_sys_mount+0x4a0/0x5a0 fs/namespace.c:3606 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x290 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x13c/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x5c/0x134 arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x128 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585 -> #0 (&ei->xattr_sem){++++}-{3:3}: check_prev_add kernel/locking/lockdep.c:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain kernel/locking/lockdep.c:3825 [inline] __lock_acquire+0x27c8/0x6610 kernel/locking/lockdep.c:5049 lock_acquire+0x20c/0x638 kernel/locking/lockdep.c:5662 down_write+0x5c/0x88 kernel/locking/rwsem.c:1573 ext4_write_lock_xattr fs/ext4/xattr.h:158 [inline] ext4_destroy_inline_data+0x30/0x114 fs/ext4/inline.c:1922 ext4_writepages+0x42c/0x28fc fs/ext4/inode.c:2763 do_writepages+0x2c4/0x50c mm/page-writeback.c:2491 __writeback_single_inode+0x164/0x157c fs/fs-writeback.c:1622 writeback_sb_inodes+0x870/0x1470 fs/fs-writeback.c:1913 wb_writeback+0x40c/0xfdc fs/fs-writeback.c:2087 wb_do_writeback fs/fs-writeback.c:2230 [inline] wb_workfn+0x360/0xe18 fs/fs-writeback.c:2270 process_one_work+0x7e4/0x13bc kernel/workqueue.c:2292 worker_thread+0x8cc/0xfe8 kernel/workqueue.c:2439 kthread+0x254/0x2e0 kernel/kthread.c:376 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:850 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 *** 3 locks held by kworker/u4:16/6249: #0: ffff0000c2c2c138 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x69c/0x13bc kernel/workqueue.c:-1 #1: ffff8000219c7c40 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x6e8/0x13bc kernel/workqueue.c:2267 #2: ffff00010c174c18 (&sbi->s_writepages_rwsem){.+.+}-{0:0}, at: ext4_writepages+0x1b0/0x28fc fs/ext4/inode.c:2717 stack backtrace: CPU: 1 PID: 6249 Comm: kworker/u4:16 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/02/2026 Workqueue: writeback wb_workfn (flush-7:5) Call trace: dump_backtrace+0x1c4/0x1f0 arch/arm64/kernel/stacktrace.c:158 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165 __dump_stack+0x30/0x40 lib/dump_stack.c:88 dump_stack_lvl+0xf4/0x15c lib/dump_stack.c:106 dump_stack+0x1c/0x5c lib/dump_stack.c:113 print_circular_bug+0x148/0x1b0 kernel/locking/lockdep.c:2048 check_noncircular+0x264/0x2f8 kernel/locking/lockdep.c:2170 check_prev_add kernel/locking/lockdep.c:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain kernel/locking/lockdep.c:3825 [inline] __lock_acquire+0x27c8/0x6610 kernel/locking/lockdep.c:5049 lock_acquire+0x20c/0x638 kernel/locking/lockdep.c:5662 down_write+0x5c/0x88 kernel/locking/rwsem.c:1573 ext4_write_lock_xattr fs/ext4/xattr.h:158 [inline] ext4_destroy_inline_data+0x30/0x114 fs/ext4/inline.c:1922 ext4_writepages+0x42c/0x28fc fs/ext4/inode.c:2763 do_writepages+0x2c4/0x50c mm/page-writeback.c:2491 __writeback_single_inode+0x164/0x157c fs/fs-writeback.c:1622 writeback_sb_inodes+0x870/0x1470 fs/fs-writeback.c:1913 wb_writeback+0x40c/0xfdc fs/fs-writeback.c:2087 wb_do_writeback fs/fs-writeback.c:2230 [inline] wb_workfn+0x360/0xe18 fs/fs-writeback.c:2270 process_one_work+0x7e4/0x13bc kernel/workqueue.c:2292 worker_thread+0x8cc/0xfe8 kernel/workqueue.c:2439 kthread+0x254/0x2e0 kernel/kthread.c:376 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:850 EXT4-fs error (device loop5): ext4_mb_generate_buddy:1126: group 0, block bitmap and bg descriptor inconsistent: 0 vs 150994969 free clusters 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=2415919504 EXT4-fs (loop5): dirty_blocks=4576 EXT4-fs (loop5): Block reservation details EXT4-fs (loop5): i_reserved_data_blocks=286 EXT4-fs (loop5): Delayed block allocation failed for inode 15 at logical offset 4 with max blocks 2048 with error 28 wlan1: Trigger new scan to find an IBSS to join wlan1: Trigger new scan to find an IBSS to join