From: David Rientjes <rientjes@google.com>
To: Wei Yang <weiyang@linux.vnet.ibm.com>
Cc: akpm@linux-foundation.org, tj@kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm/memblock: WARN_ON when nid differs from overlap region
Date: Wed, 8 Jul 2015 17:54:18 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.10.1507081750240.16585@chino.kir.corp.google.com> (raw)
In-Reply-To: <1436342488-19851-1-git-send-email-weiyang@linux.vnet.ibm.com>
On Wed, 8 Jul 2015, Wei Yang wrote:
> Each memblock_region has nid to indicates the Node ID of this range. For
> the overlap case, memblock_add_range() inserts the lower part and leave the
> upper part as indicated in the overlapped region.
>
> If the nid of the new range differs from the overlapped region, the
> information recorded is not correct.
>
> This patch adds a WARN_ON when the nid of the new range differs from the
> overlapped region.
>
> ---
>
> I am not familiar with the lower level topology, maybe this case will not
> happen.
>
> If current implementation is based on the assumption, that overlapped
> ranges' nid and flags are the same, I would suggest to add a comment to
> indicates this background.
>
> If the assumption is not correct, I suggest to add a WARN_ON or BUG_ON to
> indicates this case.
>
> Signed-off-by: Wei Yang <weiyang@linux.vnet.ibm.com>
> ---
> mm/memblock.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/mm/memblock.c b/mm/memblock.c
> index 9318b56..09efe70 100644
> --- a/mm/memblock.c
> +++ b/mm/memblock.c
> @@ -540,6 +540,9 @@ repeat:
> * area, insert that portion.
> */
> if (rbase > base) {
> +#ifdef CONFIG_HAVE_MEMBLOCK_NODE_MAP
> + WARN_ON(nid != memblock_get_region_node(rgn));
> +#endif
> nr_new++;
> if (insert)
> memblock_insert_region(type, i++, base,
I think the assertion that nid should match memblock_get_region_node() of
the overlapped region is correct. It only functionally makes a difference
if insert == true, but I don't think there's harm in verifying it
regardless.
Acked-by: David Rientjes <rientjes@google.com>
I think your supplemental to the changelog suggests that you haven't seen
this actually occur, but in the off chance that you have then it would be
interesting to see it.
--
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>
next prev parent reply other threads:[~2015-07-09 0:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 8:01 Wei Yang
2015-07-09 0:54 ` David Rientjes [this message]
2015-07-09 1:25 ` Wei Yang
2015-07-11 4:19 ` [PATCH] mm/memblock: WARN_ON when flags " Wei Yang
2015-07-16 0:19 ` David Rientjes
2015-07-16 2:23 ` Wei Yang
2015-07-16 2:34 ` [PATCH V2] " Wei Yang
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.10.1507081750240.16585@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=tj@kernel.org \
--cc=weiyang@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