From: Paul Mackerras <paulus@samba.org>
To: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
Pekka Enberg <penberg@kernel.org>,
linux-mm@kvack.org, David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Lameter <cl@linux.com>
Subject: Re: [PATCH] slab: Fix nodeid bounds check for non-contiguous node IDs
Date: Mon, 1 Dec 2014 11:42:10 +1100 [thread overview]
Message-ID: <20141201004210.GA11234@drongo> (raw)
In-Reply-To: <547BB2F0.5040708@jp.fujitsu.com>
On Mon, Dec 01, 2014 at 09:14:40AM +0900, Yasuaki Ishimatsu wrote:
> (2014/12/01 7:16), Paul Mackerras wrote:
> >The bounds check for nodeid in ____cache_alloc_node gives false
> >positives on machines where the node IDs are not contiguous, leading
> >to a panic at boot time. For example, on a POWER8 machine the node
> >IDs are typically 0, 1, 16 and 17. This means that num_online_nodes()
> >returns 4, so when ____cache_alloc_node is called with nodeid = 16 the
> >VM_BUG_ON triggers.
>
> Do you have the call trace? If you have it, please add it in the description.
I can get it easily enough.
> >To fix this, we instead compare the nodeid with MAX_NUMNODES, and
> >additionally make sure it isn't negative (since nodeid is an int).
> >The check is there mainly to protect the array dereference in the
> >get_node() call in the next line, and the array being dereferenced is
> >of size MAX_NUMNODES. If the nodeid is in range but invalid, the
> >BUG_ON in the next line will catch that.
> >
> >Signed-off-by: Paul Mackerras <paulus@samba.org>
>
> Do you need to backport it into -stable kernels?
It does need to go to stable, yes, for 3.10 and later.
> >---
> >diff --git a/mm/slab.c b/mm/slab.c
> >index eb2b2ea..f34e053 100644
> >--- a/mm/slab.c
> >+++ b/mm/slab.c
> >@@ -3076,7 +3076,7 @@ static void *____cache_alloc_node(struct kmem_cache *cachep, gfp_t flags,
> > void *obj;
> > int x;
> >
>
> >- VM_BUG_ON(nodeid > num_online_nodes());
> >+ VM_BUG_ON(nodeid < 0 || nodeid >= MAX_NUMNODES);
>
> How about use:
> VM_BUG_ON(!node_online(nodeid));
That would not be better, since node_online() doesn't bounds-check its
argument.
> When allocating the memory, the node of the memory being allocated must be
> online. But your code cannot check the condition.
The following two lines:
> > n = get_node(cachep, nodeid);
> > BUG_ON(!n);
effectively check that condition already, as I tried to explain in the
commit message.
Regards,
Paul.
next prev parent reply other threads:[~2014-12-01 0:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-30 22:16 [PATCH] slab: Fix nodeid bounds check for non-contiguous node IDs Paul Mackerras
2014-12-01 0:14 ` Yasuaki Ishimatsu
2014-12-01 0:42 ` Paul Mackerras [this message]
2014-12-01 1:17 ` Yasuaki Ishimatsu
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=20141201004210.GA11234@drongo \
--to=paulus@samba.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.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;
as well as URLs for NNTP newsgroup(s).