From: Andrew Morton <akpm@linux-foundation.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: [PATCH] mm: Make it easier to catch NULL cache names
Date: Tue, 28 Jul 2009 17:06:32 -0700 [thread overview]
Message-ID: <20090728170632.2d136ce6.akpm@linux-foundation.org> (raw)
In-Reply-To: <1248754289.30993.45.camel@pasglop>
On Tue, 28 Jul 2009 14:11:29 +1000
Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> Right now, if you inadvertently pass NULL to kmem_cache_create() at boot
> time, it crashes much later after boot somewhere deep inside sysfs which
> makes it very non obvious to figure out what's going on.
That must have been a pretty dumb piece of kernel code. It's a bit
questionable (IMO) whether we need to cater for really exceptional
bugs. But whatever.
slab used to have a check (__get_user) to see whether the ->name field
was still readable. This was to detect the case where the slab cache
was created from a kernel module and the module forgot to remove the
cache at rmmod-time. Subsequent reads of /proc/slabinfo would
confusingly go splat. The check seems to have been removed (from
slab.c, at least). If it is still there then it should be applied
consistently and across all slab versions. In which case that check
would make your patch arguably-unneeded. But it seems to have got
itself zapped.
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> ---
>
> Yes, I did hit that :-) Something in ppc land using an array of caches
> and got the names array out of sync with changes to the list of indices.
>
> mm/slub.c | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/mm/slub.c b/mm/slub.c
> index b9f1491..e31fbe6 100644
> --- a/mm/slub.c
> +++ b/mm/slub.c
> @@ -3292,6 +3292,9 @@ struct kmem_cache *kmem_cache_create(const char *name, size_t size,
> {
> struct kmem_cache *s;
>
> + if (WARN_ON(!name))
> + return NULL;
> +
> down_write(&slub_lock);
> s = find_mergeable(size, align, flags, name, ctor);
> if (s) {
Let's see:
slab.c: goes BUG
slob.c: will apparently go oops at some later time
slqb.c: does dump_stack(), returns NULL from kmem_cache_create()
slub.c: does WARN(), returns NULL from kmem_cache_create()
I think I'll apply the patch, cc Pekka then run away.
--
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:[~2009-07-29 0:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 4:11 [PATCH] mm: Make it easier to catch NULL cache names Benjamin Herrenschmidt
2009-07-29 0:06 ` Andrew Morton [this message]
2009-07-29 5:55 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2009-07-28 1:48 Benjamin Herrenschmidt
2009-07-28 2:52 ` Linus Torvalds
2009-07-28 2:55 ` Benjamin Herrenschmidt
2009-07-28 5:01 ` David Rientjes
2009-07-28 7:39 ` Benjamin Herrenschmidt
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=20090728170632.2d136ce6.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@cs.helsinki.fi \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).