From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: David Rientjes <rientjes@google.com>
Cc: linux-mm@kvack.org, Christoph Lameter <cl@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: kmem_cache_destroy() badness with SLUB
Date: Tue, 29 Jun 2010 07:44:29 +1000 [thread overview]
Message-ID: <1277761469.4200.194.camel@pasglop> (raw)
In-Reply-To: <alpine.DEB.2.00.1006280159010.28072@chino.kir.corp.google.com>
On Mon, 2010-06-28 at 02:03 -0700, David Rientjes wrote:
> On Mon, 28 Jun 2010, Benjamin Herrenschmidt wrote:
>
> > Hi folks !
> >
> > Internally, I'm hitting a little "nit"...
> >
> > sysfs_slab_add() has this check:
> >
> > if (slab_state < SYSFS)
> > /* Defer until later */
> > return 0;
> >
> > But sysfs_slab_remove() doesn't.
> >
> > So if the slab is created -and- destroyed at, for example, arch_initcall
> > time, then we hit a WARN in the kobject code, trying to dispose of a
> > non-existing kobject.
> >
> Indeed, but shouldn't we be appropriately handling the return value of
> sysfs_slab_add() so that it fails cache creation? We wouldn't be calling
> sysfs_slab_remove() on a cache that was never created.
It's eventually created, but yes, we should probably store a state,
unless we have a clean way to know the kobject in there is uninitialized
and test for that.
> > Now, at first sight, just adding the same test to sysfs_slab_remove()
> > would do the job... but it all seems very racy to me.
> >
> > I don't understand in fact how this slab_state deals with races at all.
> >
> All modifiers of slab_state are intended to be run only on the boot cpu so
> the only concern is the ordering. We need slab_state to indicate how far
> slab has been initialized since we can't otherwise enforce how code uses
> slab in between things like kmem_cache_init(), kmem_cache_init_late(), and
> initcalls on the boot cpu.
But initcalls aren't pinned to the boot CPU... IE. I don't see how the
sysfs creation avoids racing with SLAB creation, or am I missing
something ?
Cheers,
Ben.
>
> --
> 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>
--
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:[~2010-06-28 21:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 1:31 kmem_cache_destroy() badness with SLUB Benjamin Herrenschmidt
2010-06-28 9:03 ` David Rientjes
2010-06-28 21:44 ` Benjamin Herrenschmidt [this message]
2010-06-29 15:47 ` Christoph Lameter
2010-07-06 3:58 ` Roland Dreier
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=1277761469.4200.194.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.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).