[v5.15] kernel panic: kernel: panic_on_warn set ... (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c86c4726e7f0 Linux 5.15.211
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1428fb39580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6f8e2266b61925dc
dashboard link: https://syzkaller.appspot.com/bug?extid=2488c844558affa7e17a
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c3e980557785/disk-c86c4726.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5fbaf3714ad0/vmlinux-c86c4726.xz
kernel image: https://storage.googleapis.com/syzbot-assets/de60a4f1e940/bzImage-c86c4726.xz

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

RSP: 002b:00007f2a340bee58 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f2a340beee0 RCX: 00007f2a35e680ca
RDX: 0000200000000000 RSI: 0000200000000040 RDI: 00007f2a340beea0
RBP: 0000200000000000 R08: 00007f2a340beee0 R09: 0000000000000008
R10: 0000000000000008 R11: 0000000000000246 R12: 0000200000000040
R13: 00007f2a340beea0 R14: 0000000000005517 R15: 0000200000000100
</TASK>
Kernel panic - not syncing: kernel: panic_on_warn set ...
CPU: 0 PID: 5364 Comm: syz.5.248 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/2026
Call Trace:
<TASK>
dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
panic+0x2f8/0x850 kernel/panic.c:309
check_panic_on_warn kernel/panic.c:229 [inline]
__warn+0x248/0x2b0 kernel/panic.c:680
report_bug+0x1b9/0x2e0 lib/bug.c:199
handle_bug+0x3a/0x70 arch/x86/kernel/traps.c:239
exc_invalid_op+0x16/0x40 arch/x86/kernel/traps.c:259
asm_exc_invalid_op+0x16/0x20 arch/x86/include/asm/idtentry.h:604
RIP: 0010:lockdep_unregister_key+0x4d7/0x520 kernel/locking/lockdep.c:6325
Code: 80 00 00 00 75 39 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 f9 97 61 08 41 f7 c4 00 02 00 00 74 90 fb 84 db 75 8f eb a0 <0f> 0b e9 44 ff ff ff 0f 0b e9 b0 fe ff ff 0f 0b e9 fd fe ff ff e8
RSP: 0018:ffffc9000333f9c0 EFLAGS: 00010002
RAX: 0000000000000000 RBX: ffff88802c925728 RCX: dffffc0000000000
RDX: 0000000000000001 RSI: 0000000000000004 RDI: ffffc9000333f940
RBP: ffffc9000333fa90 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffff52000667f28 R12: 0000000000000202
R13: ffff88802c924000 R14: 0000000000000000 R15: 1ffff92000667f3c
f2fs_fill_super+0x3ce4/0x7050 fs/f2fs/super.c:4536
mount_bdev+0x28a/0x3c0 fs/super.c:1400
legacy_get_tree+0xe6/0x180 fs/fs_context.c:611
vfs_get_tree+0x88/0x270 fs/super.c:1530
do_new_mount+0x247/0xa40 fs/namespace.c:3034
do_mount fs/namespace.c:3377 [inline]
__do_sys_mount fs/namespace.c:3585 [inline]
__se_sys_mount+0x2e3/0x3d0 fs/namespace.c:3562
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f2a35e680ca
Code: 48 c7 c2 e8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 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:00007f2a340bee58 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f2a340beee0 RCX: 00007f2a35e680ca
RDX: 0000200000000000 RSI: 0000200000000040 RDI: 00007f2a340beea0
RBP: 0000200000000000 R08: 00007f2a340beee0 R09: 0000000000000008
R10: 0000000000000008 R11: 0000000000000246 R12: 0000200000000040
R13: 00007f2a340beea0 R14: 0000000000005517 R15: 0000200000000100
</TASK>
Shutting down cpus with NMI
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
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