All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: Aaron Tomlin <atomlin@redhat.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, glommer@parallels.com
Subject: Re: [PATCH v2] mm: slab: Verify the nodeid passed to ____cache_alloc_node
Date: Mon, 25 Feb 2013 12:45:32 -0500	[thread overview]
Message-ID: <512BA33C.6060506@redhat.com> (raw)
In-Reply-To: <591256534.8212978.1361812690861.JavaMail.root@redhat.com>

On 02/25/2013 12:18 PM, Aaron Tomlin wrote:

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

-- 
All rights reversed

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

WARNING: multiple messages have this Message-ID (diff)
From: Rik van Riel <riel@redhat.com>
To: Aaron Tomlin <atomlin@redhat.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, glommer@parallels.com
Subject: Re: [PATCH v2] mm: slab: Verify the nodeid passed to ____cache_alloc_node
Date: Mon, 25 Feb 2013 12:45:32 -0500	[thread overview]
Message-ID: <512BA33C.6060506@redhat.com> (raw)
In-Reply-To: <591256534.8212978.1361812690861.JavaMail.root@redhat.com>

On 02/25/2013 12:18 PM, Aaron Tomlin wrote:

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

-- 
All rights reversed

  reply	other threads:[~2013-02-25 17:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <813482873.8209105.1361812140956.JavaMail.root@redhat.com>
2013-02-25 17:18 ` [PATCH v2] mm: slab: Verify the nodeid passed to ____cache_alloc_node Aaron Tomlin
2013-02-25 17:18   ` Aaron Tomlin
2013-02-25 17:45   ` Rik van Riel [this message]
2013-02-25 17:45     ` Rik van Riel
2013-02-25 19:27     ` Christoph Lameter
2013-02-25 19:27       ` Christoph Lameter
     [not found] <1081382531.982691.1366726661820.JavaMail.root@redhat.com>
2013-04-23 14:31 ` [Patch " Aaron Tomlin
2013-04-23 14:31   ` Aaron Tomlin
2013-04-23 15:51   ` Christoph Lameter
2013-04-23 15:51     ` Christoph Lameter
2013-04-23 16:45   ` Rafael Aquini
2013-04-23 16:45     ` Rafael Aquini
2013-04-23 23:16   ` David Rientjes
2013-04-23 23:16     ` David Rientjes
2013-04-24  7:26   ` Pekka Enberg
2013-04-24  7:26     ` Pekka Enberg

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=512BA33C.6060506@redhat.com \
    --to=riel@redhat.com \
    --cc=atomlin@redhat.com \
    --cc=glommer@parallels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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.