From: "Ted Ts'o" <tytso@mit.edu>
To: David Rientjes <rientjes@google.com>
Cc: "Toralf Förster" <toralf.foerster@gmx.de>,
"Catalin Marinas" <catalin.marinas@arm.com>,
linux-kernel@vger.kernel.org
Subject: Re: mke2fs: page allocation failure w/ kernel 2.6.37
Date: Fri, 7 Jan 2011 18:23:39 -0500 [thread overview]
Message-ID: <20110107232339.GS21922@thunk.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1101071443280.23858@chino.kir.corp.google.com>
On Fri, Jan 07, 2011 at 02:45:30PM -0800, David Rientjes wrote:
> On Wed, 5 Jan 2011, Toralf Förster wrote:
>
> > Hello,
> >
> > I got this in /var/log/messages today (created a ext2 partition at an external USB drive, worked fine) :
> >
>
> Yeah, this failure is from the kmemleak stack which simply means that
> debugging tool will be disabled rather than any disruption to the
> workflow.
>
> I'm curious why kmemleak is masking with GFP_KERNEL and GFP_ATOMIC and not
> allowing users to pass __GFP_NOWARN to suppress this type of failure,
> especially since the stack trace is already emitted by kmemleak when it is
> stopped. Catalin?
Indeed, is there a reason why the kmemleak code is so noisy? And can
it display a more obvious message about what is going on? It took me
a while to figure out why it was unhappy, and whether there it was a
fault of the code it was testing, or just that it could get the memory
it needed....
- Ted
next prev parent reply other threads:[~2011-01-07 23:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 21:37 mke2fs: page allocation failure w/ kernel 2.6.37 Toralf Förster
2011-01-07 22:45 ` David Rientjes
2011-01-07 23:23 ` Ted Ts'o [this message]
2011-01-08 12:47 ` Catalin Marinas
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=20110107232339.GS21922@thunk.org \
--to=tytso@mit.edu \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.com \
--cc=toralf.foerster@gmx.de \
/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