From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
To: Jesper Dangaard Brouer <jbrouer@redhat.com>
Cc: Christoph Lameter <cl@linux.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm <linux-mm@kvack.org>
Subject: Re: Corruption with MMOTS slub-bulk-allocation-from-per-cpu-partial-pages.patch
Date: Tue, 9 Jun 2015 09:22:59 +0900 [thread overview]
Message-ID: <20150609002258.GA9687@js1304-P5Q-DELUXE> (raw)
In-Reply-To: <20150608121639.3d9ce2aa@redhat.com>
On Mon, Jun 08, 2015 at 12:16:39PM +0200, Jesper Dangaard Brouer wrote:
>
> It seems the patch from (inserted below):
> http://ozlabs.org/~akpm/mmots/broken-out/slub-bulk-allocation-from-per-cpu-partial-pages.patch
>
> Is not protecting access to c->partial "enough" (section is under
> local_irq_disable/enable). When exercising bulk API I can make it
> crash/corrupt memory when compiled with CONFIG_SLUB_CPU_PARTIAL=y
>
> First I suspected:
> object = get_freelist(s, c->page);
> But the problem goes way with CONFIG_SLUB_CPU_PARTIAL=n
>
>
> From: Christoph Lameter <cl@linux.com>
> Subject: slub: bulk allocation from per cpu partial pages
>
> Cover all of the per cpu objects available.
>
> Expand the bulk allocation support to drain the per cpu partial pages
> while interrupts are off.
>
> Signed-off-by: Christoph Lameter <cl@linux.com>
> Cc: Jesper Dangaard Brouer <brouer@redhat.com>
> Cc: Pekka Enberg <penberg@kernel.org>
> Cc: David Rientjes <rientjes@google.com>
> Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
> mm/slub.c | 36 +++++++++++++++++++++++++++++++++---
> 1 file changed, 33 insertions(+), 3 deletions(-)
>
> diff -puN mm/slub.c~slub-bulk-allocation-from-per-cpu-partial-pages mm/slub.c
> --- a/mm/slub.c~slub-bulk-allocation-from-per-cpu-partial-pages
> +++ a/mm/slub.c
> @@ -2769,15 +2769,45 @@ bool kmem_cache_alloc_bulk(struct kmem_c
> while (size) {
> void *object = c->freelist;
>
> - if (!object)
> - break;
> + if (unlikely(!object)) {
> + /*
> + * Check if there remotely freed objects
> + * availalbe in the page.
> + */
> + object = get_freelist(s, c->page);
> +
> + if (!object) {
> + /*
> + * All objects in use lets check if
> + * we have other per cpu partial
> + * pages that have available
> + * objects.
> + */
> + c->page = c->partial;
> + if (!c->page) {
> + /* No per cpu objects left */
> + c->freelist = NULL;
> + break;
> + }
> +
> + /* Next per cpu partial page */
> + c->partial = c->page->next;
> + c->freelist = get_freelist(s,
> + c->page);
> + continue;
> + }
> +
> + }
> +
>
> - c->freelist = get_freepointer(s, object);
> *p++ = object;
> size--;
>
> if (unlikely(flags & __GFP_ZERO))
> memset(object, 0, s->object_size);
> +
> + c->freelist = get_freepointer(s, object);
> +
Hello,
get_freepointer() should be called before zeroing object.
It may help your problem.
Thanks.
--
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-06-09 0:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 10:16 Jesper Dangaard Brouer
2015-06-09 0:22 ` Joonsoo Kim [this message]
2015-06-10 10:44 ` Jesper Dangaard Brouer
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=20150609002258.GA9687@js1304-P5Q-DELUXE \
--to=iamjoonsoo.kim@lge.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=jbrouer@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox