sched: panic on corrupted stack end
authorJann Horn <jannh@google.com>
Wed, 1 Jun 2016 09:55:07 +0000 (11:55 +0200)
committerLinus Torvalds <torvalds@linux-foundation.org>
Fri, 10 Jun 2016 19:09:43 +0000 (12:09 -0700)
commit29d6455178a09e1dc340380c582b13356227e8df
tree7bdb5e5a818ab442e8b68213bb9d589fdf7cadf7
parent2f36db71009304b3f0b95afacd8eba1f9f046b87
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>
kernel/sched/core.c