EXT4-fs error (device loop7): ext4_empty_dir:3084: inode #11: comm syz-executor: invalid size BUG: MAX_LOCKDEP_CHAINS too low! turning off the locking correctness validator. CPU: 1 UID: 0 PID: 7764 Comm: syz-executor Tainted: G L syzkaller #0 PREEMPT Tainted: [L]=SOFTLOCKUP Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/23/2026 Call trace: show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:499 (C) __dump_stack+0x30/0x40 lib/dump_stack.c:94 dump_stack_lvl+0xd8/0x12c lib/dump_stack.c:120 dump_stack+0x1c/0x28 lib/dump_stack.c:129 add_chain_cache kernel/locking/lockdep.c:-1 [inline] lookup_chain_cache_add kernel/locking/lockdep.c:3899 [inline] validate_chain kernel/locking/lockdep.c:3920 [inline] __lock_acquire+0xed4/0x2b08 kernel/locking/lockdep.c:5288 lock_acquire+0x13c/0x320 kernel/locking/lockdep.c:5942 __raw_spin_lock_irq include/linux/spinlock_api_smp.h:165 [inline] _raw_spin_lock_irq+0x58/0x70 kernel/locking/spinlock.c:189 spin_lock_irq include/linux/spinlock.h:377 [inline] loop_queue_work drivers/block/loop.c:710 [inline] loop_queue_rq+0x204/0xa08 drivers/block/loop.c:1811 __blk_mq_issue_directly+0xfc/0x298 block/blk-mq.c:2718 blk_mq_try_issue_directly+0xe0/0x22c block/blk-mq.c:2778 blk_mq_submit_bio+0x1930/0x227c block/blk-mq.c:3236 __submit_bio+0x94/0x2dc block/blk-core.c:674 __submit_bio_noacct_mq block/blk-core.c:757 [inline] submit_bio_noacct_nocheck+0x290/0xa14 block/blk-core.c:791 submit_bio_noacct+0xd80/0x16e8 block/blk-core.c:929 submit_bio+0x2d0/0x410 block/blk-core.c:970 blk_crypto_submit_bio include/linux/blk-crypto.h:212 [inline] __bh_submit+0x6a0/0x7bc fs/buffer.c:1136 bh_submit+0x3c/0x50 fs/buffer.c:1150 ext4_commit_super+0x26c/0x458 fs/ext4/super.c:6415 ext4_handle_error+0x330/0x554 fs/ext4/super.c:736 __ext4_error_inode+0x274/0x3d0 fs/ext4/super.c:882 ext4_empty_dir+0x198/0x9dc fs/ext4/namei.c:3084 ext4_rmdir+0x200/0x8bc fs/ext4/namei.c:3173 vfs_rmdir+0x354/0x5e4 fs/namei.c:5533 filename_rmdir+0x208/0x3fc fs/namei.c:5590 __do_sys_unlinkat fs/namei.c:5765 [inline] __se_sys_unlinkat fs/namei.c:5758 [inline] __arm64_sys_unlinkat+0xcc/0x108 fs/namei.c:5758 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x244 arch/arm64/kernel/syscall.c:49 el0_svc_common+0xec/0x23c arch/arm64/kernel/syscall.c:121 do_el0_svc+0x4c/0x5c arch/arm64/kernel/syscall.c:140 el0_svc+0x60/0x1d8 arch/arm64/kernel/entry-common.c:796 el0t_64_sync_handler+0x44/0x104 arch/arm64/kernel/entry-common.c:815 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:606 EXT4-fs error (device loop7): ext4_empty_dir:3084: inode #11: comm syz-executor: invalid size EXT4-fs error (device loop7): ext4_empty_dir:3084: inode #11: comm syz-executor: invalid size EXT4-fs error (device loop7): ext4_empty_dir:3084: inode #11: comm syz-executor: invalid size EXT4-fs error (device loop7): ext4_empty_dir:3084: inode #11: comm syz-executor: invalid size EXT4-fs error (device loop7): ext4_empty_dir:3084: inode #11: comm syz-executor: invalid size EXT4-fs error (device loop7): ext4_empty_dir:3084: inode #11: comm syz-executor: invalid size EXT4-fs error (device loop7): ext4_empty_dir:3084: inode #11: comm syz-executor: invalid size EXT4-fs error (device loop7): ext4_empty_dir:3084: inode #11: comm syz-executor: invalid size EXT4-fs error (device loop7): ext4_empty_dir:3084: inode #11: comm syz-executor: invalid size EXT4-fs (loop7): unmounting filesystem 00000000-0000-0000-0000-000000000000.