From: JoonSoo Kim <js1304@gmail.com>
To: Christoph Lameter <cl@linux.com>
Cc: Pekka Enberg <penberg@kernel.org>,
Glauber Costa <glommer@parallels.com>,
linux-mm@kvack.org, David Rientjes <rientjes@google.com>
Subject: Re: CK2 [03/15] slub: Use a statically allocated kmem_cache boot structure for bootstrap
Date: Tue, 2 Oct 2012 23:47:36 +0900 [thread overview]
Message-ID: <CAAmzW4NW4LgXOxXQvRVgBhJ2Vxyijx0bugGDPgBjz2kUY=DAuA@mail.gmail.com> (raw)
In-Reply-To: <0000013a0e5f601a-e8401015-afdb-4958-b562-0d1d5d2d6f15-000000@email.amazonses.com>
Hi, Christoph.
2012/9/29 Christoph Lameter <cl@linux.com>:
> @@ -3930,6 +3905,10 @@ int __kmem_cache_create(struct kmem_cach
> if (err)
> return err;
>
> + /* Mutex is not taken during early boot */
> + if (slab_state <= UP)
> + return 0;
> +
> mutex_unlock(&slab_mutex);
> err = sysfs_slab_add(s);
> mutex_lock(&slab_mutex);
This addition should go to previous patch "create common functions for
boot slab creation".
In there, create_boot_cache() call __kmem_cache_create(), and then
mutex_unlock() is called without taking mutext.
--
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-10-02 14:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120928191715.368450474@linux.com>
2012-09-28 19:18 ` CK2 [02/15] create common functions for boot slab creation Christoph Lameter
2012-09-28 19:18 ` CK2 [01/15] slab: Simplify bootstrap Christoph Lameter
2012-09-28 19:23 ` CK2 [15/15] Move kmalloc_node functions to common code Christoph Lameter
2012-09-28 19:24 ` CK2 [07/15] slab: Use common kmalloc_index/kmalloc_size functions Christoph Lameter
2012-10-02 15:10 ` JoonSoo Kim
2012-10-03 15:06 ` Christoph Lameter
2012-09-28 19:24 ` CK2 [14/15] Common Kmalloc cache determination Christoph Lameter
2012-09-28 19:24 ` CK2 [12/15] Common function to create the kmalloc array Christoph Lameter
2012-09-28 19:25 ` CK2 [04/15] slab: Use the new create_boot_cache function to simplify bootstrap Christoph Lameter
2012-10-02 14:56 ` JoonSoo Kim
2012-10-03 14:55 ` Christoph Lameter
2012-09-28 19:25 ` CK2 [11/15] Common definition for the array of kmalloc caches Christoph Lameter
2012-09-28 19:25 ` CK2 [05/15] Common alignment code Christoph Lameter
2012-09-28 19:34 ` CK2 [03/15] slub: Use a statically allocated kmem_cache boot structure for bootstrap Christoph Lameter
2012-10-02 14:47 ` JoonSoo Kim [this message]
2012-10-03 14:50 ` Christoph Lameter
2012-09-28 19:34 ` CK2 [10/15] Common constants for kmalloc boundaries Christoph Lameter
2012-09-28 19:34 ` CK2 [08/15] slab: Common name for the per node structures Christoph Lameter
2012-09-28 19:39 ` CK2 [06/15] Common kmalloc slab index determination Christoph Lameter
2012-09-28 19:39 ` CK2 [13/15] stat: Use size_t for sizes instead of unsigned Christoph Lameter
2012-09-28 19:59 ` CK2 [09/15] slab: rename nodelists to node Christoph Lameter
[not found] <20121019142254.724806786@linux.com>
2012-10-19 14:51 ` CK2 [03/15] slub: Use a statically allocated kmem_cache boot structure for bootstrap 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='CAAmzW4NW4LgXOxXQvRVgBhJ2Vxyijx0bugGDPgBjz2kUY=DAuA@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