From: Christoph Lameter <cl@linux.com>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Michal Hocko <mhocko@suse.cz>, Pekka Enberg <penberg@kernel.org>,
Matt Mackall <mpm@selenic.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: mm: slub: gpf in deactivate_slab
Date: Mon, 7 Apr 2014 14:34:56 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.10.1404071429530.4447@nuc> (raw)
In-Reply-To: <53401F56.5090507@oracle.com>
On Sat, 5 Apr 2014, Sasha Levin wrote:
> [ 1035.193166] Call Trace:
> [ 1035.193166] ? init_object (mm/slub.c:679)
> [ 1035.193166] setup_object.isra.34 (mm/slub.c:1071 mm/slub.c:1399)
> [ 1035.193166] new_slab (mm/slub.c:286 mm/slub.c:1439)
> [ 1035.193166] __slab_alloc (mm/slub.c:2203 mm/slub.c:2363)
> [ 1035.193166] ? kmem_cache_alloc (mm/slub.c:2469 mm/slub.c:2480 mm/slub.c:2485)
Ok so the story here is that slub decided it needed a new slab and
requested memory from the page allocator.
setup_object() tries to write to the page which fails.
Could the page allocator have delivered a reference to a page struct that
creates an invalid address?
The code that fails is:
page = allocate_slab(s,
flags & (GFP_RECLAIM_MASK | GFP_CONSTRAINT_MASK), node);
if (!page)
goto out;
--- So we got a page from teh page allocator
order = compound_order(page);
inc_slabs_node(s, page_to_nid(page), page->objects);
memcg_bind_pages(s, order);
page->slab_cache = s;
__SetPageSlab(page);
-- Writing to the page struct works.
if (page->pfmemalloc)
SetPageSlabPfmemalloc(page);
start = page_address(page);
if (unlikely(s->flags & SLAB_POISON))
memset(start, POISON_INUSE, PAGE_SIZE << order);
--- This should have triggered since we write to the page but maybe this
slab has a ctor set and therefore no poisining is possible.
last = start;
for_each_object(p, s, start, page->objects) {
setup_object(s, page, last);
*** This is where the write access to the page fails.
set_freepointer(s, last, p);
last = p;
}
setup_object(s, page, last);
--
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-04-07 19:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 16:25 Sasha Levin
2014-03-25 15:54 ` Sasha Levin
2014-03-25 16:51 ` Christoph Lameter
2014-03-25 16:52 ` Michal Hocko
2014-03-25 17:06 ` Christoph Lameter
2014-03-25 17:15 ` Sasha Levin
2014-03-25 18:10 ` Christoph Lameter
2014-03-26 0:17 ` Sasha Levin
2014-03-26 15:43 ` Christoph Lameter
2014-04-05 15:20 ` Sasha Levin
2014-04-07 17:13 ` Christoph Lameter
2014-04-07 17:16 ` Sasha Levin
2014-04-07 19:34 ` Christoph Lameter [this message]
2014-03-25 17:56 ` Michal Hocko
2014-03-25 18:01 ` Michal Hocko
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=alpine.DEB.2.10.1404071429530.4447@nuc \
--to=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=mpm@selenic.com \
--cc=penberg@kernel.org \
--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