Re: [PATCH] panic: add TAINT_SOFTLOCKUP

Nick Krause
2014-06-25T02:21:16Z

I second David, there is no reason for this if there is a bug due to
page allocation
failure it will be probably at the point of kernel panic or in the
trace statements
at panic.
Cheers Nick

On Tue, Jun 24, 2014 at 10:19 PM, Nick Krause <xerofoify@gmail.com> wrote:
> I second David, this is no reason for this if there is a bug due to page
> allocation
> failure it will be probably at the point of kernel panic or in the trace
> statements
> at panic.
> Cheers Nick
>
>
> On Tue, Jun 24, 2014 at 8:45 PM, David Rientjes <rientjes@google.com> wrote:
>>
>> On Tue, 24 Jun 2014, Josh Hunt wrote:
>>
>> > Anyone you'd suggest adding to this thread to get other feedback about
>> > tracking page allocation failures? I could also spin up a patch and cc
>> > them.
>> >
>>
>> Page allocation failures happen all the time, mostly because of
>> large-order allocations (more than PAGE_ALLOC_COSTLY_ORDER) or allocations
>> done with GFP_ATOMIC where it's impossible to reclaim or compact memory to
>> allocate. Because of this, they are fairly easy to trigger from userspace
>> without having to do much.
>>
>> Why would this qualify for a taint? I have never debugged a kernel crash
>> that I traced back to an earlier page allocation failure and said "oh, if
>> I had only known about that page allocation failure earlier!". If one of
>> them is going to cause an issue, it probably is at the point of the crash
>> and you shouldn't have to "investigate" much.
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
>
>