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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 83a7eefedc9b Linux 6.10-rc3
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=102f2ede980000
kernel config: https://syzkaller.appspot.com/x/.config?x=fae227a1534ac4c3
dashboard link: https://syzkaller.appspot.com/bug?extid=d0b85a6325bf10d1b2d9
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 lu...@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-83a7eefe.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/83ac9da5b8b8/vmlinux-83a7eefe.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1798fbabb1d9/Image-83a7eefe.xz

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

Kernel panic - not syncing: corrupted stack end detected inside scheduler
CPU: 0 PID: 16 Comm: ksoftirqd/0 Not tainted 6.10.0-rc3-syzkaller-g83a7eefedc9b #0
Hardware name: riscv-virtio,qemu (DT)
Call Trace:
[<ffffffff8000f6f8>] dump_backtrace+0x2e/0x3c arch/riscv/kernel/stacktrace.c:129
[<ffffffff85c253c4>] show_stack+0x34/0x40 arch/riscv/kernel/stacktrace.c:135
[<ffffffff85c7f13c>] __dump_stack lib/dump_stack.c:88 [inline]
[<ffffffff85c7f13c>] dump_stack_lvl+0x108/0x196 lib/dump_stack.c:114
[<ffffffff85c7f1e6>] dump_stack+0x1c/0x24 lib/dump_stack.c:123
[<ffffffff85c25f8a>] panic+0x382/0x800 kernel/panic.c:347
[<ffffffff85c8e0ec>] schedule_debug kernel/sched/core.c:5962 [inline]
[<ffffffff85c8e0ec>] __schedule+0x342e/0x3486 kernel/sched/core.c:6628
[<ffffffff85c8f0e4>] preempt_schedule_irq+0x7a/0x1a8 kernel/sched/core.c:7067
[<ffffffff85c828ca>] raw_irqentry_exit_cond_resched kernel/entry/common.c:311 [inline]
[<ffffffff85c828ca>] raw_irqentry_exit_cond_resched kernel/entry/common.c:303 [inline]
[<ffffffff85c828ca>] irqentry_exit+0x138/0x17a kernel/entry/common.c:354
[<ffffffff85c81562>] do_irq+0x34/0x4a arch/riscv/kernel/traps.c:390
[<ffffffff85ca3d18>] ret_from_exception+0x0/0x64 arch/riscv/kernel/entry.S:112
[<ffffffff800dab7a>] arch_local_irq_enable arch/riscv/include/asm/irqflags.h:21 [inline]
[<ffffffff800dab7a>] ksoftirqd_run_end kernel/softirq.c:411 [inline]
[<ffffffff800dab7a>] run_ksoftirqd kernel/softirq.c:929 [inline]
[<ffffffff800dab7a>] run_ksoftirqd+0xda/0x144 kernel/softirq.c:920
[<ffffffff801639e2>] smpboot_thread_fn+0x654/0xb9c kernel/smpboot.c:164
[<ffffffff8014d7e4>] kthread+0x28c/0x3a6 kernel/kthread.c:389
[<ffffffff85ca3e22>] ret_from_fork+0xe/0x1c arch/riscv/kernel/entry.S:232
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