Commit 29d64551 authored by Jann Horn's avatar Jann Horn Committed by Linus Torvalds
Browse files

sched: panic on corrupted stack end

Until now, hitting this BUG_ON caused a recursive oops (because oops
handling involves do_exit(), which calls into the scheduler, which in
turn raises an oops), which caused stuff below the stack to be
overwritten until a panic happened (e.g.  via an oops in interrupt
context, caused by the overwritten CPU index in the thread_info).

Just panic directly.
Signed-off-by: default avatarJann Horn <>
Signed-off-by: default avatarLinus Torvalds <>
parent 2f36db71
......@@ -3047,7 +3047,8 @@ static noinline void __schedule_bug(struct task_struct *prev)
static inline void schedule_debug(struct task_struct *prev)
if (task_stack_end_corrupted(prev))
panic("corrupted stack end detected inside scheduler\n");
if (unlikely(in_atomic_preempt_off())) {
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment