[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.0905040353290.24987@chino.kir.corp.google.com>
Date: Mon, 4 May 2009 03:56:10 -0700 (PDT)
From: David Rientjes <rientjes@...gle.com>
To: Cyrill Gorcunov <gorcunov@...il.com>
cc: Pekka Enberg <penberg@...helsinki.fi>, Ingo Molnar <mingo@...e.hu>,
Jack Steiner <steiner@....com>,
Andrew Morton <akpm@...ux-foundation.org>,
"H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>,
Christoph Lameter <cl@...ux-foundation.org>
Subject: Re: introducing __GFP_PANIC
On Mon, 4 May 2009, Cyrill Gorcunov wrote:
> @@ -1685,7 +1687,12 @@ nopage:
> dump_stack();
> show_mem();
> }
> - return page;
> + if (unlikely((gfp_mask & __GFP_PANIC))) {
Too many parentheses and this doesn't need the unnecessary braces.
> + panic("Out of memory: panic due to __GFP_PANIC.\n"
> + "%s order:%d, mode:0x%x\n", p->comm,
> + order, gfp_mask);
The extra newline in this statement doesn't seem necessary, it's just one
less line that will be visible on the frozen screen. I also think calling
this 'gfp_mask' instead of 'mode' is more appropriate just like the oom
killer does.
> + }
> + return NULL;
> got_pg:
> if (kmemcheck_enabled)
> kmemcheck_pagealloc_alloc(page, order, gfp_mask);
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists