From: Cyrill Gorcunov <gorcunov@gmail.com>
To: David Rientjes <rientjes@google.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
Ingo Molnar <mingo@elte.hu>, Jack Steiner <steiner@sgi.com>,
Andrew Morton <akpm@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Christoph Lameter <cl@linux-foundation.org>
Subject: Re: introducing __GFP_PANIC
Date: Mon, 4 May 2009 15:10:14 +0400 [thread overview]
Message-ID: <20090504111014.GG4173@lenovo> (raw)
In-Reply-To: <alpine.DEB.2.00.0905040353290.24987@chino.kir.corp.google.com>
[David Rientjes - Mon, May 04, 2009 at 03:56:10AM -0700]
| 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.
Thanks David, fixed (old games /with other flags/ rudiment).
|
| > + 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.
ok, convinced. Maybe even make it shorter like
"Panic due to __GFP_PANIC: %s order:%d, gfp_mask:0x%x\n"
Hmm?
|
| > + }
| > + return NULL;
| > got_pg:
| > if (kmemcheck_enabled)
| > kmemcheck_pagealloc_alloc(page, order, gfp_mask);
| >
|
-- Cyrill
next prev parent reply other threads:[~2009-05-04 11:10 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-01 19:56 [PATCH -tip] x86: uv - prevent NULL dereference in uv_system_init Cyrill Gorcunov
2009-05-01 20:03 ` Ingo Molnar
2009-05-01 20:09 ` Cyrill Gorcunov
2009-05-01 20:25 ` Cyrill Gorcunov
2009-05-01 20:31 ` Jack Steiner
2009-05-03 8:48 ` Ingo Molnar
2009-05-03 9:01 ` Cyrill Gorcunov
2009-05-03 9:09 ` David Rientjes
2009-05-03 9:38 ` Cyrill Gorcunov
2009-05-03 9:53 ` David Rientjes
2009-05-03 9:59 ` Pekka Enberg
2009-05-03 12:12 ` Cyrill Gorcunov
2009-05-03 12:27 ` Pekka Enberg
2009-05-03 14:38 ` Cyrill Gorcunov
2009-05-03 16:54 ` Pekka Enberg
2009-05-03 17:23 ` introducing __GFP_PANIC Cyrill Gorcunov
2009-05-03 17:38 ` Pekka Enberg
2009-05-03 17:49 ` Cyrill Gorcunov
2009-05-03 20:45 ` Cyrill Gorcunov
2009-05-03 20:58 ` David Rientjes
2009-05-04 8:14 ` Cyrill Gorcunov
2009-05-04 8:32 ` Pekka Enberg
2009-05-04 8:49 ` Cyrill Gorcunov
2009-05-04 9:56 ` Pekka Enberg
2009-05-04 9:08 ` Cyrill Gorcunov
2009-05-04 9:57 ` Pekka Enberg
2009-05-04 10:01 ` Cyrill Gorcunov
2009-05-04 10:11 ` Cyrill Gorcunov
2009-05-04 10:33 ` Pekka Enberg
2009-05-04 10:52 ` Cyrill Gorcunov
2009-05-04 10:56 ` David Rientjes
2009-05-04 11:10 ` Cyrill Gorcunov [this message]
2009-05-04 16:58 ` [tip:x86/apic] x86: uv - prevent NULL dereference in uv_system_init() tip-bot for Cyrill Gorcunov
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=20090504111014.GG4173@lenovo \
--to=gorcunov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=rientjes@google.com \
--cc=steiner@sgi.com \
--cc=tglx@linutronix.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