Messages in this thread | | | Date | Mon, 19 Dec 2011 10:34:21 -0800 | From | Andi Kleen <> | Subject | Re: [PATCH] panic: Don't print redundant backtraces on oops |
| |
it?
> I think the two problems are not related. My problem was that only one > CPU should execute panic. Andi's problem is that one (or more oops) > messages are scrolled away by a subsequent panic.
Yes it's just for making panic less chatty.
> But I am not sure if Andi's patch solves all his problems. What e.g. > about panic_on_oom? Don't we have the same problem here?
Yes, it only solves it for this specific -- but common -- case. Or at least it was a case that annoyed me and prompted me to write the patch :)
I had a patch some time ago for a xpanic() where the caller could pass in additional flags, including one to disable the backtrace. But that was a much larger patch, this was a simpler alternative.
-Andi
| |