tree 7bdb5e5a818ab442e8b68213bb9d589fdf7cadf7
parent 2f36db71009304b3f0b95afacd8eba1f9f046b87
author Jann Horn <jannh@google.com> 1464774907 +0200
committer Linus Torvalds <torvalds@linux-foundation.org> 1465585783 -0700

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>