From: JoonSoo Kim <js1304@gmail.com>
To: Christoph Lameter <cl@linux.com>
Cc: Glauber Costa <glommer@parallels.com>,
Pekka Enberg <penberg@kernel.org>,
linux-mm@kvack.org, David Rientjes <rientjes@google.com>
Subject: Re: Common10 [10/20] Move duping of slab name to slab_common.c
Date: Sun, 5 Aug 2012 02:34:21 +0900 [thread overview]
Message-ID: <CAAmzW4MoHp9YXg1Y48edh2TEdR8wUYYdxE7nq5WkgCRb9fRUXw@mail.gmail.com> (raw)
In-Reply-To: <20120803192153.623879087@linux.com>
2012/8/4 Christoph Lameter <cl@linux.com>:
> Duping of the slabname has to be done by each slab. Moving this code
> to slab_common avoids duplicate implementations.
>
> With this patch we have common string handling for all slab allocators.
> Strings passed to kmem_cache_create() are copied internally. Subsystems
> can create temporary strings to create slab caches.
>
> Slabs allocated in early states of bootstrap will never be freed (and those
> can never be freed since they are essential to slab allocator operations).
> During bootstrap we therefore do not have to worry about duping names.
>
> Signed-off-by: Christoph Lameter <cl@linux.com>
We can remove some comment for name param of __kmem_cache_create() in slab.c.
> Index: linux-2.6/mm/slab_common.c
> ===================================================================
> --- linux-2.6.orig/mm/slab_common.c 2012-08-03 09:02:50.000000000 -0500
> +++ linux-2.6/mm/slab_common.c 2012-08-03 09:02:54.900587462 -0500
> @@ -54,6 +54,7 @@ struct kmem_cache *kmem_cache_create(con
> {
> struct kmem_cache *s;
> int err = 0;
> + char *n;
>
> #ifdef CONFIG_DEBUG_VM
> if (!name || in_interrupt() || size < sizeof(void *) ||
> @@ -93,16 +94,26 @@ struct kmem_cache *kmem_cache_create(con
> WARN_ON(strchr(name, ' ')); /* It confuses parsers */
> #endif
>
> - s = __kmem_cache_create(name, size, align, flags, ctor);
> - if (!s)
> - err = -ENOSYS; /* Until __kmem_cache_create returns code */
> + n = kstrdup(name, GFP_KERNEL);
> + if (!n) {
> + err = -ENOMEM;
> + goto out_locked;
> + }
> +
> + s = __kmem_cache_create(n, size, align, flags, ctor);
We need to remove CONFIG_DEBUG_VM for out_locked now,
although later patch handles it.
> - /*
> - * Check if the slab has actually been created and if it was a
> - * real instatiation. Aliases do not belong on the list
> - */
> - if (s && s->refcount == 1)
> - list_add(&s->list, &slab_caches);
> + if (s) {
> + /*
> + * Check if the slab has actually been created and if it was a
> + * real instatiation. Aliases do not belong on the list
> + */
> + if (s->refcount == 1)
> + list_add(&s->list, &slab_caches);
> +
> + } else {
> + kfree(n);
> + err = -ENOSYS; /* Until __kmem_cache_create returns code */
> + }
In mergeable case, leak for name is possible.
__kmem_cache_create() doesn't set name to s->name in mergeable case.
So, this memory can't be freed.
--
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:[~2012-08-04 17:34 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 19:20 Common10 [00/20] Sl[auo]b: Common code rework V10 Christoph Lameter
2012-08-03 19:20 ` Common10 [01/20] slub: Add debugging to verify correct cache use on kmem_cache_free() Christoph Lameter
2012-08-03 19:20 ` Common10 [02/20] slub: Use kmem_cache for the kmem_cache structure Christoph Lameter
2012-08-03 19:20 ` Common10 [03/20] Rename oops label Christoph Lameter
2012-08-03 19:20 ` Common10 [04/20] Improve error handling in kmem_cache_create Christoph Lameter
2012-08-03 19:20 ` Common10 [05/20] Move list_add() to slab_common.c Christoph Lameter
2012-08-04 17:01 ` JoonSoo Kim
2012-08-08 14:47 ` Christoph Lameter (Open Source)
2012-08-03 19:20 ` Common10 [06/20] Extract a common function for kmem_cache_destroy Christoph Lameter
2012-08-04 17:21 ` JoonSoo Kim
2012-08-08 14:51 ` Christoph Lameter (Open Source)
2012-08-03 19:20 ` Common10 [07/20] Always use the name "kmem_cache" for the slab cache with the kmem_cache structure Christoph Lameter
2012-08-03 19:21 ` Common10 [08/20] Move freeing of kmem_cache structure to common code Christoph Lameter
2012-08-03 19:21 ` Common10 [09/20] Get rid of __kmem_cache_destroy Christoph Lameter
2012-08-03 19:21 ` Common10 [10/20] Move duping of slab name to slab_common.c Christoph Lameter
2012-08-04 17:34 ` JoonSoo Kim [this message]
2012-08-08 14:59 ` Christoph Lameter (Open Source)
2012-08-14 18:42 ` JoonSoo Kim
2012-08-03 19:21 ` Common10 [11/20] Do slab aliasing call from common code Christoph Lameter
2012-08-04 17:44 ` JoonSoo Kim
2012-08-08 15:40 ` Christoph Lameter (Open Source)
2012-08-03 19:21 ` Common10 [12/20] Move sysfs_slab_add to common Christoph Lameter
2012-08-04 17:46 ` JoonSoo Kim
2012-08-08 15:51 ` Christoph Lameter (Open Source)
2012-08-03 19:21 ` Common10 [13/20] Move kmem_cache allocations into common code Christoph Lameter
2012-08-04 17:48 ` JoonSoo Kim
2012-08-08 17:31 ` Christoph Lameter (Open Source)
2012-08-08 13:51 ` Glauber Costa
2012-08-08 17:56 ` Christoph Lameter (Open Source)
2012-08-03 19:21 ` Common10 [14/20] Shrink __kmem_cache_create() parameter lists Christoph Lameter
2012-08-08 13:15 ` Glauber Costa
2012-08-08 17:45 ` Christoph Lameter (Open Source)
2012-08-03 19:21 ` Common10 [15/20] Move kmem_cache refcounting to common code Christoph Lameter
2012-08-03 19:21 ` Common10 [16/20] slub: Use a statically allocated kmem_cache boot structure for bootstrap Christoph Lameter
2012-08-04 17:50 ` JoonSoo Kim
2012-08-03 19:21 ` Common10 [17/20] slab: Simplify bootstrap Christoph Lameter
2012-08-03 19:21 ` Common10 [18/20] create common functions for boot slab creation Christoph Lameter
2012-08-03 19:21 ` Common10 [19/20] slab: Use the new create_boot_cache function to simplify bootstrap Christoph Lameter
2012-08-03 19:21 ` Common10 [20/20] Common alignment code 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=CAAmzW4MoHp9YXg1Y48edh2TEdR8wUYYdxE7nq5WkgCRb9fRUXw@mail.gmail.com \
--to=js1304@gmail.com \
--cc=cl@linux.com \
--cc=glommer@parallels.com \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.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).