mirror of
https://github.com/Fishwaldo/linux-bl808.git
synced 2025-03-19 05:24:11 +00:00
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: Jann Horn <jannh@google.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
parent
2f36db7100
commit
29d6455178
1 changed files with 2 additions and 1 deletions
|
@ -3047,7 +3047,8 @@ static noinline void __schedule_bug(struct task_struct *prev)
|
||||||
static inline void schedule_debug(struct task_struct *prev)
|
static inline void schedule_debug(struct task_struct *prev)
|
||||||
{
|
{
|
||||||
#ifdef CONFIG_SCHED_STACK_END_CHECK
|
#ifdef CONFIG_SCHED_STACK_END_CHECK
|
||||||
BUG_ON(task_stack_end_corrupted(prev));
|
if (task_stack_end_corrupted(prev))
|
||||||
|
panic("corrupted stack end detected inside scheduler\n");
|
||||||
#endif
|
#endif
|
||||||
|
|
||||||
if (unlikely(in_atomic_preempt_off())) {
|
if (unlikely(in_atomic_preempt_off())) {
|
||||||
|
|
Loading…
Add table
Reference in a new issue