syzbot


kernel panic: stack is corrupted in ring_buffer_record_off

Status: closed as invalid on 2024/09/13 08:06
Subsystems: kernel
[Documentation on labels]
First crash: 182d, last: 182d

Sample crash report:
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: ring_buffer_record_off+0x27d/0x280
CPU: 1 UID: 0 PID: 6084 Comm: syz.0.147 Not tainted 6.11.0-rc4-next-20240820-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/0x870 kernel/panic.c:354
 __stack_chk_fail+0x15/0x20 kernel/panic.c:827
 ring_buffer_record_off+0x27d/0x280
 </TASK>
Shutting down cpus with NMI
Kernel Offset: disabled
Rebooting in 86400 seconds..

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/08/20 11:15 linux-next bb1b0acdcd66 9f0ab3fb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in ring_buffer_record_off
* Struck through repros no longer work on HEAD.