[v5.15] WARNING in console_trylock_spinning

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 0c935c049b5c Linux 5.15.179
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13f5f83f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=98c228fbc016eb3a
dashboard link: https://syzkaller.appspot.com/bug?extid=71caa8b4bf909c83dd61
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d5477072f336/disk-0c935c04.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/77d15907ffb3/vmlinux-0c935c04.xz
kernel image: https://storage.googleapis.com/syzbot-assets/efe5d79cb16a/Image-0c935c04.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+71caa8...@syzkaller.appspotmail.com

EXT2-fs (loop4): error: ext2_free_branches: Read failure, inode=16, block=4294965504
EXT2-fs (loop4): error: ext2_free_branches: Read failure, inode=16, block=4294967295
------------[ cut here ]------------
WARNING: CPU: 0 PID: 4033 at fs/inode.c:332 drop_nlink+0xe8/0x148 fs/inode.c:332
Modules linked in:
CPU: 0 PID: 4033 Comm: syz-executor Not tainted 5.15.179-syzkaller #0
BUG: MAX_LOCKDEP_CHAINS too low!
turning off the locking correctness validator.
CPU: 0 PID: 4033 Comm: syz-executor Not tainted 5.15.179-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Call trace:
dump_backtrace+0x0/0x530 arch/arm64/kernel/stacktrace.c:152
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
dump_stack+0x1c/0x58 lib/dump_stack.c:113
lookup_chain_cache_add kernel/locking/lockdep.c:3735 [inline]
validate_chain kernel/locking/lockdep.c:3756 [inline]
__lock_acquire+0x1b64/0x7638 kernel/locking/lockdep.c:5012
lock_acquire+0x240/0x77c kernel/locking/lockdep.c:5623
console_trylock_spinning+0x110/0x288 kernel/printk/printk.c:1896
vprintk_emit+0x124/0x21c kernel/printk/printk.c:2273
vprintk_default+0xa0/0xe4 kernel/printk/printk.c:2289
vprintk+0x200/0x2d4 kernel/printk/printk_safe.c:45
_printk+0xdc/0x128 kernel/printk/printk.c:2299
dump_stack_print_info+0x104/0x1a0 lib/dump_stack.c:57
show_regs_print_info+0x20/0x34 lib/dump_stack.c:82
__show_regs+0xd0/0x710 arch/arm64/kernel/process.c:215
show_regs+0x20/0x44 arch/arm64/kernel/process.c:245
__warn+0x13c/0x490 kernel/panic.c:678
report_bug+0x164/0x288 lib/bug.c:199
bug_handler+0x50/0x1fc arch/arm64/kernel/traps.c:954
call_break_hook arch/arm64/kernel/debug-monitors.c:321 [inline]
brk_handler+0x17c/0x2e4 arch/arm64/kernel/debug-monitors.c:328
do_debug_exception+0x20c/0x430 arch/arm64/mm/fault.c:908
el1_dbg+0x64/0x80 arch/arm64/kernel/entry-common.c:398
el1h_64_sync_handler+0x40/0xac arch/arm64/kernel/entry-common.c:438
el1h_64_sync+0x78/0x7c arch/arm64/kernel/entry.S:522
drop_nlink+0xe8/0x148 fs/inode.c:332
inode_dec_link_count include/linux/fs.h:2503 [inline]
ext2_unlink+0x1b4/0x218 fs/ext2/namei.c:302
vfs_unlink+0x2f0/0x508 fs/namei.c:4280
do_unlinkat+0x4cc/0x830 fs/namei.c:4348
__do_sys_unlinkat fs/namei.c:4391 [inline]
__se_sys_unlinkat fs/namei.c:4384 [inline]
__arm64_sys_unlinkat+0xcc/0xfc fs/namei.c:4384
__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+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : drop_nlink+0xe8/0x148 fs/inode.c:332
lr : drop_nlink+0xe8/0x148 fs/inode.c:332
sp : ffff8000200b7a00
x29: ffff8000200b7a00 x28: 1ffff00004016f50 x27: 1ffff00004016f4c
x26: dfff800000000000 x25: ffff700004016f48 x24: ffff8000200b7a80
x23: 1fffe0001d3ccc42 x22: dfff800000000000 x21: 0000000000000000
x20: ffff0000e9e66210 x19: ffff0000e9e661c8 x18: 0000000000000000
x17: 0000000000000000 x16: ffff800011b5ac80 x15: 000000000000000d
x14: 1ffff0000296e06c x13: 0000000000000000 x12: 00000000000000fa
x11: 0000000000000000 x10: 0000000000000000 x9 : ffff0000c8768000
x8 : ffff8000089ec1a4 x7 : 0000000000000000 x6 : 00000000000000fa
x5 : ffff0000e9e66250 x4 : ffff0000de17cf00 x3 : ffff800008ecde28
x2 : 0000000000000010 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
drop_nlink+0xe8/0x148 fs/inode.c:332
inode_dec_link_count include/linux/fs.h:2503 [inline]
ext2_unlink+0x1b4/0x218 fs/ext2/namei.c:302
vfs_unlink+0x2f0/0x508 fs/namei.c:4280
do_unlinkat+0x4cc/0x830 fs/namei.c:4348
__do_sys_unlinkat fs/namei.c:4391 [inline]
__se_sys_unlinkat fs/namei.c:4384 [inline]
__arm64_sys_unlinkat+0xcc/0xfc fs/namei.c:4384
__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+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
irq event stamp: 1958016
hardirqs last enabled at (1958015): [<ffff8000083c78a8>] seqcount_lockdep_reader_access+0x208/0x2cc include/linux/seqlock.h:105
hardirqs last disabled at (1958016): [<ffff800011b56334>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:396
softirqs last enabled at (1957910): [<ffff8000080309b8>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:31
softirqs last disabled at (1957908): [<ffff800008030984>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:18
---[ end trace 37b3ebd3defcd8df ]---


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.