Skip to main content

Browse the archive

Revision 29d6455178a09e1dc340380c582b13356227e8df authored by Jann Horn on 01 June 2016, 09:55:07 UTC, committed by Linus Torvalds on 10 June 2016, 19:09:43 UTC 
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>
1 parent 2f36db7
History
File Mode Size
r128_cce.bin.ihex -rw-r--r-- 5.5 KB
back to top