[lkml]   [2010]   [Nov]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PROBLEM] WARNING: at kernel/exit.c:910 do_exit
On 11/21, Linus Torvalds wrote:
> I do wonder if we should just flag a thread as "busy oopsing" before
> we call "do_exit(), so that _if_ we do a recursive oops we
> (a) don't print it out (except just a one-liner to say "recursively
> oopsed in %pS" or something)
> (b) don't try to clean up with do_exit (because that's likely just
> going to oops again or run out of stack etc)
> That might have left us with a more visible original oops. Maybe the
> register contents at that point could have given us any ideas (ie
> things like the slab poisoning memory patterns or whatever).

+inf ;)

I thought about this many times. To me, the major offender is
__schedule_bug(). It is quite useful by itself, but every bug with
spinlock held triggers it.


 \ /
  Last update: 2010-11-21 20:39    [W:0.035 / U:3.220 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site