syzbot


kernel panic: stack is corrupted in __switch_to

Status: closed as invalid on 2024/09/13 10:29
First crash: 180d, last: 175d

Sample crash report:
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: __switch_to+0xe9d/0x1c30
CPU: 0 UID: 0 PID: 5366 Comm: syz.2.14 Not tainted 6.11.0-rc5-next-20240827-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120
 panic+0x349/0x880 kernel/panic.c:354
 __stack_chk_fail+0x15/0x20 kernel/panic.c:836
 __switch_to+0xe9d/0x1c30
 </TASK>
Shutting down cpus with NMI
Kernel Offset: disabled
Rebooting in 86400 seconds..

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/08/28 07:37 linux-next 6f923748057a 6c853ff9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __switch_to
2024/08/23 07:49 linux-next c79c85875f1a ce8a9099 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __switch_to
2024/08/22 17:54 linux-next 6a7917c89f21 295a4b50 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __switch_to
* Struck through repros no longer work on HEAD.