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
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
File | Mode | Size |
---|---|---|
Kconfig | -rw-r--r-- | 365 bytes |
Makefile | -rw-r--r-- | 261 bytes |
async_memcpy.c | -rw-r--r-- | 3.2 KB |
async_pq.c | -rw-r--r-- | 13.0 KB |
async_raid6_recov.c | -rw-r--r-- | 14.9 KB |
async_tx.c | -rw-r--r-- | 7.7 KB |
async_xor.c | -rw-r--r-- | 9.8 KB |
raid6test.c | -rw-r--r-- | 6.5 KB |
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...