From: David Rientjes <rientjes@google.com>
To: Josh Hunt <johunt@akamai.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Baron, Jason" <jbaron@akamai.com>
Subject: Re: [PATCH] panic: add TAINT_SOFTLOCKUP
Date: Tue, 24 Jun 2014 17:45:13 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1406241740330.22030@chino.kir.corp.google.com> (raw)
In-Reply-To: <53A9899C.9040005@akamai.com>
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.
next prev parent reply other threads:[~2014-06-25 0:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 2:12 Josh Hunt
2014-06-23 22:11 ` Andrew Morton
2014-06-23 22:45 ` Josh Hunt
2014-06-23 22:51 ` Andrew Morton
2014-06-24 14:22 ` Josh Hunt
2014-06-24 15:06 ` Dave Jones
2014-06-24 15:20 ` Dave Jones
2014-06-25 0:45 ` David Rientjes [this message]
[not found] ` <CAPDOMVifbWCohymLyCc6cxG7t9WCDLTbCWRZx8xyG3DOMFqKqg@mail.gmail.com>
2014-06-25 2:21 ` Nick Krause
2014-06-25 3:24 ` Josh Hunt
2014-06-25 3:39 ` Nick Krause
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1406241740330.22030@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=jbaron@akamai.com \
--cc=johunt@akamai.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®