linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Glauber Costa <glommer@parallels.com>
To: Christoph Lameter <cl@linux.com>
Cc: Pekka Enberg <penberg@kernel.org>, Joonsoo Kim <js1304@gmail.com>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	linux-mm@kvack.org, David Rientjes <rientjes@google.com>
Subject: Re: C13 [08/14] Get rid of __kmem_cache_destroy
Date: Wed, 5 Sep 2012 12:25:17 +0400	[thread overview]
Message-ID: <50470C6D.201@parallels.com> (raw)
In-Reply-To: <00000139937082ef-c61760a5-47fe-42d9-a043-ba81b2dfd216-000000@email.amazonses.com>

On 09/05/2012 02:39 AM, Christoph Lameter wrote:
> On Mon, 3 Sep 2012, Glauber Costa wrote:
> 
>> Here is the code for that in slab_common.c:
>>
>>     if (!__kmem_cache_shutdown(s)) {
>>         if (s->flags & SLAB_DESTROY_BY_RCU)
>>             rcu_barrier();
>>
>>         __kmem_cache_destroy(s);
>>     } ...
>>
>> All that code that used to belong in __kmem_cache_destroy(), will not be
>> executed in kmem_cache_shutdown() without an rcu_barrier.
> 
> But that allocator specific code in __kmem_cache_destroy will not free the
> kmem_cache structure. That is the only important thing to be aware of.
> Only deferred frees of slab pages may still be in progress at this time
> until the close of the RCU period. These deferred freeing actions do not
> refer to anything but the kmem_cache structure. Therefore the rest can be
> freed before the period is over. And we check that the rest can be freed.
> Should there be a leftover at that point then f.e.
> free_partial() will issue a warning.
> 

Ok. That sounds reasonable.
(not sure if correct, but reasonable)

> kmem_cache_destroy() can only be called after all objects have been freed
> and it checks that this actually was done. "Have been freed" means in the
> context of an SLAB_DESTROY_BY_RCU slab that the rcu delayed frees for the
> individual objects are complete. During kmem_cache_destroy() only slab
> pages that contain no objects are freed back to the page allocator. Those
> will be also freed in a deferred way at kmem_cache_destroy. Hmmm.... we
> could simply delete the SLAB_DESTROY_BY_RCU flag and free the objects
> without obeying the rcu period since no objects should be allocated at
> that point.
> 
>> You need at least Paul's ack here to guarantee it is safe, but I believe
>> it is not. Take a look for instance at 7ed9f7e5db5, which describes a
>> subtle bug arising from such a situation.
> 
> The commit that you referred to ensures that kmem_cache is not freed
> before the rcu period is over. This patch does not change that guarantee.
> 
> --
> 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>

  reply	other threads:[~2012-09-05  8:28 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120824160903.168122683@linux.com>
2012-08-24 16:10 ` C13 [05/14] Extract a common function for kmem_cache_destroy Christoph Lameter
2012-09-03 14:41   ` Glauber Costa
2012-09-03 15:26   ` Glauber Costa
2012-09-04 22:58     ` Christoph Lameter
2012-08-24 16:12 ` C13 [08/14] Get rid of __kmem_cache_destroy Christoph Lameter
2012-09-03 14:58   ` Glauber Costa
2012-09-04 22:39     ` Christoph Lameter
2012-09-05  8:25       ` Glauber Costa [this message]
2012-08-24 16:12 ` C13 [07/14] Move freeing of kmem_cache structure to common code Christoph Lameter
2012-09-03 14:51   ` Glauber Costa
2012-08-24 16:17 ` C13 [03/14] Improve error handling in kmem_cache_create Christoph Lameter
2012-09-03 14:30   ` Glauber Costa
2012-08-24 16:17 ` C13 [11/14] Move sysfs_slab_add to common Christoph Lameter
2012-09-03 15:09   ` Glauber Costa
2012-08-24 16:17 ` C13 [12/14] Move kmem_cache allocations into common code Christoph Lameter
2012-09-03 15:24   ` Glauber Costa
2012-08-24 16:17 ` C13 [06/14] Always use the name "kmem_cache" for the slab cache with the kmem_cache structure Christoph Lameter
2012-08-24 16:17 ` C13 [10/14] Do slab aliasing call from common code Christoph Lameter
2012-08-24 16:17 ` C13 [04/14] Move list_add() to slab_common.c Christoph Lameter
2012-08-24 16:17 ` C13 [01/14] slub: Add debugging to verify correct cache use on kmem_cache_free() Christoph Lameter
2012-09-03 14:26   ` Glauber Costa
2012-08-24 16:17 ` C13 [09/14] Move duping of slab name to slab_common.c Christoph Lameter
2012-09-03 15:02   ` Glauber Costa
2012-08-24 16:17 ` C13 [14/14] Move kmem_cache refcounting to common code Christoph Lameter
2012-09-03 15:12   ` Glauber Costa
2012-09-04 19:10     ` Christoph Lameter
2012-08-24 16:17 ` C13 [02/14] slub: Use kmem_cache for the kmem_cache structure Christoph Lameter
2012-09-03 14:27   ` Glauber Costa
2012-08-24 16:17 ` C13 [13/14] Shrink __kmem_cache_create() parameter lists Christoph Lameter
2012-09-03 15:33   ` Glauber Costa
2012-09-03 15:35     ` Glauber Costa
2012-09-04 22:48       ` 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=50470C6D.201@parallels.com \
    --to=glommer@parallels.com \
    --cc=cl@linux.com \
    --cc=js1304@gmail.com \
    --cc=linux-mm@kvack.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --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).