linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: JoonSoo Kim <js1304@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Christoph Lameter <cl@linux-foundation.org>,
	Pekka Enberg <penberg@kernel.org>, Matt Mackall <mpm@selenic.com>,
	linux-mm@kvack.org
Subject: Re: slab vs. slub kmem cache name inconsistency
Date: Tue, 2 Oct 2012 20:05:48 +0900	[thread overview]
Message-ID: <CAAmzW4OvWVfHhqs3puzArvVoNp4ZopZXdc38RVmFBkMd_LjNWA@mail.gmail.com> (raw)
In-Reply-To: <1349170840.10698.14.camel@jlt4.sipsolutions.net>

Hi, Johannes.

2012/10/2 Johannes Berg <johannes@sipsolutions.net>:
> Hi,
>
> I just noticed that slub's kmem_cache_create() will kstrdup() the name,
> while slab doesn't. That's a little confusing, since when you look at
> slub you can easily get away with passing a string you built on the
> stack, while that will then lead to very strange results (and possibly
> crashes?) with slab.

As far as I know, this issue is already fixed. However, fix for this
is not merged into mainline yet.
You can find the fix in common_for_cgroups branch of Pekka's git tree.

git://git.kernel.org/pub/scm/linux/kernel/git/penberg/linux.git
slab/common-for-cgroups

--
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>

  reply	other threads:[~2012-10-02 11:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-02  9:40 Johannes Berg
2012-10-02 11:05 ` JoonSoo Kim [this message]
2012-10-02 11:08   ` Johannes Berg
2012-10-02 14:43 ` Christoph Lameter

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=CAAmzW4OvWVfHhqs3puzArvVoNp4ZopZXdc38RVmFBkMd_LjNWA@mail.gmail.com \
    --to=js1304@gmail.com \
    --cc=cl@linux-foundation.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-mm@kvack.org \
    --cc=mpm@selenic.com \
    --cc=penberg@kernel.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