From: Rafael Aquini <aquini@redhat.com>
To: Aaron Tomlin <atomlin@redhat.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, cl@linux.com,
penberg@kernel.org, Rik <riel@redhat.com>
Subject: Re: [Patch v2] mm: slab: Verify the nodeid passed to ____cache_alloc_node
Date: Tue, 23 Apr 2013 13:45:28 -0300 [thread overview]
Message-ID: <20130423164528.GC16695@optiplex.redhat.com> (raw)
In-Reply-To: <1014891011.990074.1366727496599.JavaMail.root@redhat.com>
On Tue, Apr 23, 2013 at 10:31:36AM -0400, Aaron Tomlin wrote:
> Hi,
>
> This patch is in response to BZ#42967 [1].
> Using VM_BUG_ON so it's used only when CONFIG_DEBUG_VM is set,
> given that ____cache_alloc_node() is a hot code path.
>
This seems to be a valid condition to BUG_ON, though.
> Cheers,
> Aaron
>
> [1]: https://bugzilla.kernel.org/show_bug.cgi?id=42967
>
> ---8<---
> mm: slab: Verify the nodeid passed to ____cache_alloc_node
>
> If the nodeid is > num_online_nodes() this can cause an
> Oops and a panic(). The purpose of this patch is to assert
> if this condition is true to aid debugging efforts rather
> than some random NULL pointer dereference or page fault.
>
> Signed-off-by: Aaron Tomlin <atomlin@redhat.com>
> Reviewed-by: Rik van Riel <riel@redhat.com>
>
Acked-by: Rafael Aquini <aquini@redhat.com>
>
> slab.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/mm/slab.c b/mm/slab.c
> index e7667a3..735e8bd 100644
> --- a/mm/slab.c
> +++ b/mm/slab.c
> -3412,6 +3412,7 @@ static void *____cache_alloc_node(struct kmem_cache *cachep, gfp_t flags,
> void *obj;
> int x;
>
> + VM_BUG_ON(nodeid > num_online_nodes());
> l3 = cachep->nodelists[nodeid];
> BUG_ON(!l3);
next prev parent reply other threads:[~2013-04-23 16:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1081382531.982691.1366726661820.JavaMail.root@redhat.com>
2013-04-23 14:31 ` [Patch v2] mm: slab: Verify the nodeid passed to ____cache_alloc_node Aaron Tomlin
2013-04-23 15:51 ` Christoph Lameter
2013-04-23 16:45 ` Rafael Aquini [this message]
2013-04-23 23:16 ` David Rientjes
2013-04-24 7:26 ` Pekka Enberg
[not found] <813482873.8209105.1361812140956.JavaMail.root@redhat.com>
2013-02-25 17:18 ` [PATCH " Aaron Tomlin
2013-02-25 17:45 ` Rik van Riel
2013-02-25 19:27 ` Christoph Lameter
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=20130423164528.GC16695@optiplex.redhat.com \
--to=aquini@redhat.com \
--cc=atomlin@redhat.com \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=riel@redhat.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