Re: mke2fs: page allocation failure w/ kernel 2.6.37

From: Ted Ts'o
Date: Fri Jan 07 2011 - 18:24:06 EST

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
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at