[moderation] [kernel?] kernel panic: corrupted stack end in lock_is_held_type

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: a11dd49dcb93 riscv: Sparse-Memory/vmemmap out-of-bounds fix
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes
console output: https://syzkaller.appspot.com/x/log.txt?x=162e20ca180000
kernel config: https://syzkaller.appspot.com/x/.config?x=877e61347079aad5
dashboard link: https://syzkaller.appspot.com/bug?extid=a54e9bf5c27e0f0d54d7
compiler: riscv64-linux-gnu-gcc (Debian 12.2.0-13) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: riscv64
CC: [linux-...@vger.kernel.org pet...@infradead.org tg...@linutronix.de]

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

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/a741b348759c/non_bootable_disk-a11dd49d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4817c127e0bf/vmlinux-a11dd49d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/92d04cef6fb6/Image-a11dd49d.xz

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

Kernel panic - not syncing: corrupted stack end detected inside scheduler
CPU: 0 PID: 16 Comm: ksoftirqd/0 Not tainted 6.8.0-rc1-syzkaller-00030-ga11dd49dcb93 #0
Hardware name: riscv-virtio,qemu (DT)
Call Trace:
[<ffffffff80010a1e>] dump_backtrace+0x2e/0x3c arch/riscv/kernel/stacktrace.c:121
[<ffffffff858be468>] show_stack+0x34/0x40 arch/riscv/kernel/stacktrace.c:127
[<ffffffff85919934>] __dump_stack lib/dump_stack.c:88 [inline]
[<ffffffff85919934>] dump_stack_lvl+0xe8/0x154 lib/dump_stack.c:106
[<ffffffff859199bc>] dump_stack+0x1c/0x24 lib/dump_stack.c:113
[<ffffffff858beec0>] panic+0x33c/0x77c kernel/panic.c:344
[<ffffffff85927690>] schedule_debug kernel/sched/core.c:5954 [inline]
[<ffffffff85927690>] __schedule+0x313e/0x3196 kernel/sched/core.c:6620
[<ffffffff85927d64>] preempt_schedule_notrace+0xe0/0x2a2 kernel/sched/core.c:6997
[<ffffffff8591c1bc>] lockdep_enabled kernel/locking/lockdep.c:119 [inline]
[<ffffffff8591c1bc>] lock_is_held_type+0x72/0x182 kernel/locking/lockdep.c:5818
[<ffffffff801697ee>] lock_is_held include/linux/lockdep.h:231 [inline]
[<ffffffff801697ee>] __might_resched+0x2b4/0x5fc kernel/sched/core.c:10138
[<ffffffff800d3a96>] run_ksoftirqd kernel/softirq.c:923 [inline]
[<ffffffff800d3a96>] run_ksoftirqd+0xec/0x124 kernel/softirq.c:913
[<ffffffff80155b50>] smpboot_thread_fn+0x654/0xb98 kernel/smpboot.c:164
[<ffffffff80145558>] kthread+0x28c/0x3a6 kernel/kthread.c:388
[<ffffffff8593d1f6>] ret_from_fork+0xe/0x1c arch/riscv/kernel/entry.S:229
SMP: stopping secondary CPUs
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