linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: Gavin Shan <shangw@linux.vnet.ibm.com>
Cc: linux-mm@kvack.org, minchan@kernel.org, mgorman@suse.de,
	akpm@linux-foundation.org
Subject: Re: [PATCH] mm/buddy: get the allownodes for dump at once
Date: Wed, 20 Jun 2012 18:19:38 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.1206201815100.3702@chino.kir.corp.google.com> (raw)
In-Reply-To: <1339662910-25774-1-git-send-email-shangw@linux.vnet.ibm.com>

On Thu, 14 Jun 2012, Gavin Shan wrote:

> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index 7892f84..211004e 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -2765,11 +2765,19 @@ out:
>   */
>  void show_free_areas(unsigned int filter)
>  {
> -	int cpu;
> +	int nid, cpu;
> +	nodemask_t allownodes;
>  	struct zone *zone;
>  

I saw this added to the -mm tree today, but it has to be nacked with 
apologies for not seeing the patch on the mailing list earlier.

show_free_areas() is called by the oom killer, so we know two things: it 
can be called potentially very deep in the callchain and current is out of 
memory.  Both are killers for this patch since you're allocating 
nodemask_t on the stack here which could cause an overflow and because you 
can't easily fix that case with NODEMASK_ALLOC() since it allocates slab 
with GFP_KERNEL when we we're oom, which would simply suppress vital 
meminfo from being shown.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2012-06-21  1:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14  8:35 Gavin Shan
2012-06-18  2:57 ` Cong Wang
2012-06-18  3:13   ` Gavin Shan
2012-06-21  1:19 ` David Rientjes [this message]
2012-06-21  4:47   ` Gavin Shan
2012-06-21  5:13     ` David Rientjes
2012-06-21  5:16       ` Gavin Shan
2012-06-21  9:03   ` Cong Wang
2012-06-21  9:11     ` Gavin Shan

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.00.1206201815100.3702@chino.kir.corp.google.com \
    --to=rientjes@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=minchan@kernel.org \
    --cc=shangw@linux.vnet.ibm.com \
    /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