syzbot


kernel panic: corrupted stack end in worker_thread

Status: auto-closed as invalid on 2021/07/02 05:00
Subsystems: kernel
[Documentation on labels]
Reported-by: syzbot+c00f813f1abd441c4cfd@syzkaller.appspotmail.com
First crash: 1533d, last: 1533d

Sample crash report:
Kernel panic - not syncing: corrupted stack end detected inside scheduler
CPU: 1 PID: 8411 Comm: kworker/u4:6 Not tainted 5.12.0-rc8-next-20210423-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue:  0x0 (flush-8:0)
Call Trace:
 __dump_stack lib/dump_stack.c:79 [inline]
 dump_stack+0x141/0x1d7 lib/dump_stack.c:120
 panic+0x306/0x73d kernel/panic.c:231
 schedule_debug kernel/sched/core.c:4893 [inline]
 __schedule+0x23ac/0x23c0 kernel/sched/core.c:5038
 schedule+0xcf/0x270 kernel/sched/core.c:5226
 worker_thread+0x14c/0x1120 kernel/workqueue.c:2442
 kthread+0x3b1/0x4a0 kernel/kthread.c:313
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294
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
2021/05/03 04:59 linux-next e3d35712f85a 77e2b668 .config console log report info ci-upstream-linux-next-kasan-gce-root kernel panic: corrupted stack end in worker_thread
* Struck through repros no longer work on HEAD.