Patch "sched: panic on corrupted stack end" has been added to the 3.18-stable tree
Subsystems (2)
This is a note to let you know that I've just added the patch titled
sched: panic on corrupted stack end
to the 3.18-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
sched-panic-on-corrupted-stack-end.patch
and it can be found in the queue-3.18 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.
Quoted 1 line
From
29d6455178a09e1dc340380c582b13356227e8dfMon Sep 17 00:00:00 2001
From: Jann Horn <[email protected]>
Date: Wed, 1 Jun 2016 11:55:07 +0200
Subject: sched: panic on corrupted stack end
From: Jann Horn <[email protected]>
commit 29d6455178a09e1dc340380c582b13356227e8df upstream.
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.
--- kernel/sched/core.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
kernel/sched/core.c +2 -1
@@ -2709,7 +2709,8 @@ static noinline void __schedule_bug(strustatic inline void schedule_debug (struct task_struct *prev) {#ifdef CONFIG_SCHED_STACK_END_CHECK -BUG_ON (unlikely (task_stack_end_corrupted (prev))); +if (task_stack_end_corrupted (prev)) +panic ("corrupted stack end detected inside scheduler\n" );#endif /* * Test if we are atomic. Since do_exit() needs to call into
Patches currently in stable-queue which might be from [email protected] are
queue-3.18/sched-panic-on-corrupted-stack-end.patch