kernel panic: corrupted stack end detected inside scheduler (2)

kernel panic: corrupted stack end detected inside scheduler (2)

Status: closed as invalid on 2017/12/06 12:42
Subsystems: kernel
[Documentation on labels]
Reported-by: syzbot+e2601e57dce076ad33ea22bcc98bfd4bde8dedbf@syzkaller.appspotmail.com
First crash: 2341d, last: 2341d

▶ ▼ Similar bugs (2)

Kernel	Title	Repro	Cause bisect	Fix bisect	Count	Last	Reported	Patched	Status
upstream	kernel panic: corrupted stack end detected inside scheduler	C			1	2428d	2428d	0/26	closed as invalid on 2017/08/27 08:48
upstream	kernel panic: corrupted stack end detected inside scheduler (3) mm	C			1958	1936d	2086d	0/26	closed as dup on 2019/01/04 11:19

Sample crash report:

Kernel panic - not syncing: corrupted stack end detected inside scheduler

CPU: 1 PID: 4033 Comm: kworker/u4:10 Not tainted 4.14.0+ #126
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 __dump_stack lib/dump_stack.c:17 [inline]
 dump_stack+0x194/0x257 lib/dump_stack.c:53
 panic+0x1e4/0x41c kernel/panic.c:183
 schedule_debug kernel/sched/core.c:3190 [inline]
 __schedule+0x1aa0/0x2060 kernel/sched/core.c:3299
 schedule+0xf5/0x430 kernel/sched/core.c:3434
 worker_thread+0x492/0x1990 kernel/workqueue.c:2267
 kthread+0x37a/0x440 kernel/kthread.c:238
 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:437
Dumping ftrace buffer:
   (ftrace buffer empty)
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
2017/11/20 15:08	net-next-old	1deab8ce2c91	84dd36ba	.config	console log	report					ci-upstream-net-kasan-gce

* ~~Struck through~~ repros no longer work on HEAD.