From: Wei Yang <weiyang@linux.vnet.ibm.com>
To: Christoph Lameter <cl@gentwo.org>
Cc: David Rientjes <rientjes@google.com>,
Sasha Levin <sasha.levin@oracle.com>,
Wei Yang <weiyang@linux.vnet.ibm.com>,
Pekka Enberg <penberg@kernel.org>, Matt Mackall <mpm@selenic.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Dave Jones <davej@redhat.com>
Subject: Re: mm: slub: invalid memory access in setup_object
Date: Wed, 2 Jul 2014 10:04:54 +0800 [thread overview]
Message-ID: <20140702020454.GA6961@richard> (raw)
In-Reply-To: <alpine.DEB.2.11.1407010956470.5353@gentwo.org>
On Tue, Jul 01, 2014 at 09:58:52AM -0500, Christoph Lameter wrote:
>On Mon, 30 Jun 2014, David Rientjes wrote:
>
>> It's not at all clear to me that that patch is correct. Wei?
>
>Looks ok to me. But I do not like the convoluted code in new_slab() which
>Wei's patch does not make easier to read. Makes it difficult for the
>reader to see whats going on.
My patch is somewhat convoluted since I wanted to preserve the original logic
and make minimal change. And yes, it looks not that nice to audience.
I feel a little hurt by this patch. What I found and worked is gone with this
patch.
>
>Lets drop the use of the variable named "last".
>
>
>Subject: slub: Only call setup_object once for each object
>
>Modify the logic for object initialization to be less convoluted
>and initialize an object only once.
>
>Signed-off-by: Christoph Lameter <cl@linux.com>
>
>Index: linux/mm/slub.c
>===================================================================
>--- linux.orig/mm/slub.c 2014-07-01 09:50:02.486846653 -0500
>+++ linux/mm/slub.c 2014-07-01 09:52:07.918802585 -0500
>@@ -1409,7 +1409,6 @@ static struct page *new_slab(struct kmem
> {
> struct page *page;
> void *start;
>- void *last;
> void *p;
> int order;
>
>@@ -1432,15 +1431,11 @@ static struct page *new_slab(struct kmem
> if (unlikely(s->flags & SLAB_POISON))
> memset(start, POISON_INUSE, PAGE_SIZE << order);
>
>- last = start;
> for_each_object(p, s, start, page->objects) {
>- setup_object(s, page, last);
>- set_freepointer(s, last, p);
>- last = p;
>+ setup_object(s, page, p);
>+ set_freepointer(s, p, p + s->size);
> }
>- setup_object(s, page, last);
>- set_freepointer(s, last, NULL);
>-
>+ set_freepointer(s, start + (page->objects - 1) * s->size, NULL);
> page->freelist = start;
> page->inuse = page->objects;
> page->frozen = 1;
--
Richard Yang
Help you, Help me
--
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:[~2014-07-02 2:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 16:51 mm: slub: invalid memory access in setup_object Sasha Levin
2014-06-25 17:30 ` Christoph Lameter
2014-06-30 22:03 ` David Rientjes
2014-07-01 1:40 ` Wei Yang
2014-07-01 14:58 ` Christoph Lameter
2014-07-01 21:49 ` Andrew Morton
2014-07-01 21:52 ` Sasha Levin
2014-07-02 14:44 ` Christoph Lameter
2014-07-02 2:06 ` Wei Yang
2014-07-02 15:07 ` Christoph Lameter
2014-07-03 2:23 ` Wei Yang
2014-07-02 2:04 ` Wei Yang [this message]
2014-07-02 14:20 ` Christoph Lameter
2014-07-03 12:40 ` Wei Yang
2014-07-07 13:51 ` Christoph Lameter
2014-07-08 1:34 ` 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=20140702020454.GA6961@richard \
--to=weiyang@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=sasha.levin@oracle.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).