BUG: MAX_LOCKDEP_CHAINS too low! turning off the locking correctness validator. CPU: 0 PID: 10494 Comm: syz.7.2187 Not tainted 5.15.185-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 Call trace: dump_backtrace+0x0/0x43c arch/arm64/kernel/stacktrace.c:152 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216 __dump_stack+0x30/0x40 lib/dump_stack.c:88 dump_stack_lvl+0xf8/0x160 lib/dump_stack.c:106 dump_stack+0x1c/0x5c lib/dump_stack.c:113 add_chain_cache kernel/locking/lockdep.c:-1 [inline] lookup_chain_cache_add kernel/locking/lockdep.c:3735 [inline] validate_chain kernel/locking/lockdep.c:3756 [inline] __lock_acquire+0x1b30/0x651c kernel/locking/lockdep.c:5012 lock_acquire+0x1f4/0x620 kernel/locking/lockdep.c:5623 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline] _raw_spin_lock_irqsave+0xc4/0x14c kernel/locking/spinlock.c:162 try_to_wake_up+0x60/0xa64 kernel/sched/core.c:4030 wake_up_process+0x18/0x24 kernel/sched/core.c:4215 wake_up_worker kernel/workqueue.c:859 [inline] insert_work+0x2b4/0x388 kernel/workqueue.c:1381 __queue_work+0xb30/0x1054 kernel/workqueue.c:1532 queue_work_on+0xc4/0x17c kernel/workqueue.c:1559 queue_work include/linux/workqueue.h:512 [inline] loop_queue_work drivers/block/loop.c:1068 [inline] loop_queue_rq+0x97c/0xac0 drivers/block/loop.c:2202 __blk_mq_issue_directly block/blk-mq.c:2014 [inline] __blk_mq_try_issue_directly+0x3e8/0x69c block/blk-mq.c:2070 blk_mq_try_issue_directly+0xb8/0x270 block/blk-mq.c:2101 blk_mq_submit_bio+0xcf8/0x1698 block/blk-mq.c:-1 __submit_bio+0x5ec/0x624 block/blk-core.c:917 __submit_bio_noacct_mq block/blk-core.c:997 [inline] submit_bio_noacct+0x52c/0x624 block/blk-core.c:1027 submit_bio+0x374/0x5e0 block/blk-core.c:1089 submit_bh_wbc+0x4a8/0x5f8 fs/buffer.c:3056 submit_bh+0x3c/0x54 fs/buffer.c:3062 __ext4_read_bh fs/ext4/super.c:156 [inline] ext4_read_bh+0x170/0x2a0 fs/ext4/super.c:180 ext4_read_inode_bitmap+0x64c/0xfdc fs/ext4/ialloc.c:197 __ext4_new_inode+0xd08/0x32b0 fs/ext4/ialloc.c:1059 ext4_mkdir+0x328/0xa40 fs/ext4/namei.c:3066 vfs_mkdir+0x314/0x4d4 fs/namei.c:4065 do_mkdirat+0x1bc/0x508 fs/namei.c:4090 __do_sys_mkdirat fs/namei.c:4105 [inline] __se_sys_mkdirat fs/namei.c:4103 [inline] __arm64_sys_mkdirat+0x90/0xa8 fs/namei.c:4103 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181 el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608 el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584 EXT4-fs error (device loop7): ext4_do_update_inode:5203: inode #2: comm syz.7.2187: corrupted inode contents EXT4-fs error (device loop7): ext4_dirty_inode:6039: inode #2: comm syz.7.2187: mark_inode_dirty error EXT4-fs error (device loop7): ext4_do_update_inode:5203: inode #2: comm syz.7.2187: corrupted inode contents EXT4-fs error (device loop7): __ext4_ext_dirty:183: inode #2: comm syz.7.2187: mark_inode_dirty error EXT4-fs error (device loop7): ext4_do_update_inode:5203: inode #2: comm syz.7.2187: corrupted inode contents EXT4-fs error (device loop7): ext4_dirty_inode:6039: inode #2: comm syz.7.2187: mark_inode_dirty error