All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Li Zhong <zhong@linux.vnet.ibm.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm <linux-mm@kvack.org>,
	John Allen <jallen@linux.vnet.ibm.com>,
	qiuxishi@huawei.com, iamjoonsoo.kim@lge.com,
	n-horiguchi@ah.jp.nec.com, rientjes@google.com,
	Michal Hocko <mhocko@suse.cz>,
	Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Subject: Re: [PATCH] mm, page_alloc: warn about empty nodemask
Date: Tue, 20 Sep 2016 10:27:27 +0200	[thread overview]
Message-ID: <dbdc5abe-3dcd-2b93-32be-0d6da69458fd@suse.cz> (raw)
In-Reply-To: <D1029A5D-C180-440C-8B14-A6C9E17CDB06@linux.vnet.ibm.com>

On 09/09/2016 06:03 AM, Li Zhong wrote:
>
>>> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
>>> index a2214c6..d624ff3 100644
>>> --- a/mm/page_alloc.c
>>> +++ b/mm/page_alloc.c
>>> @@ -3448,6 +3448,12 @@ __alloc_pages_slowpath(gfp_t gfp_mask, unsigned int order,
>>> 	if (page)
>>> 		goto got_pg;
>>>
>>> +	if (ac->nodemask && nodes_empty(*ac->nodemask)) {
>>> +		pr_warn("nodemask is empty\n");
>>> +		gfp_mask &= ~__GFP_NOWARN;
>>> +		goto nopage;
>>> +	}
>>> +
>>
>> Wouldn't it be better to do
>>
>> 	if (WARN_ON(ac->nodemask && nodes_empty(*ac->nodemask)) {
>> 		...
>>
>> so we can identify the misbehaving call site?
>
> I think with __GFP_NOWARN cleared, we could know the call site from warn_alloc_failed().
> And the message a??nodemask is emptya?? makes the error obvious without going to the source.

Yes, that was my suggestion. It uses the generic warn_alloc_failed() this way. 
With a WARN_ON we would either have to "return NULL" (and get only the WARN_ON 
without the extra warn_alloc_failed() stuff) or "goto nopage" and thus get two 
backtraces. But this should be really rare occurence, so I don't have a 
particularly strong preference.

Anyway, since I suggested it in the first place:
Acked-by: Vlastimil Babka <vbabka@suse.cz>

> Thanks, Zhong
>

--
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>

  reply	other threads:[~2016-09-20  8:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-05  2:59 [PATCH] mem-hotplug: Don't clear the only node in new_node_page() Li Zhong
2016-09-05 14:18 ` Vlastimil Babka
2016-09-06  8:13   ` Li Zhong
2016-09-06 14:12     ` Vlastimil Babka
2016-09-07  0:41       ` [PATCH] mm, page_alloc: warn about empty nodemask Li Zhong
2016-09-08 23:26         ` Andrew Morton
2016-09-09  4:03           ` Li Zhong
2016-09-20  8:27             ` Vlastimil Babka [this message]
2016-09-12  9:18   ` [PATCH] mem-hotplug: Don't clear the only node in new_node_page() Michal Hocko
2016-09-20  8:31     ` Vlastimil Babka
2016-09-20 21:53       ` David Rientjes
2016-09-21  2:11         ` Li Zhong
2016-09-21  8:38         ` [PATCH] mem-hotplug: Use nodes that contain memory as mask " Li Zhong
2016-09-21  9:34           ` Vlastimil Babka
2016-09-21 18:14           ` Michal Hocko
2016-09-21 18:08         ` [PATCH] mem-hotplug: Don't clear the only node " Michal Hocko
2016-09-06 13:16 ` Xishi Qiu

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=dbdc5abe-3dcd-2b93-32be-0d6da69458fd@suse.cz \
    --to=vbabka@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=jallen@linux.vnet.ibm.com \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    --cc=n-horiguchi@ah.jp.nec.com \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=qiuxishi@huawei.com \
    --cc=rientjes@google.com \
    --cc=zhong@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.