Re: Adding pool_cache_invalidate_local() to pool_cache(9) API

[Jean-Yves Migeon <jeanyves.migeon%free.fr@localhost>]

On Fri, 09 Oct 2009 11:51:09 +0200, Jean-Yves Migeon
<jeanyves.migeon%free.fr@localhost> wrote:
> On Fri, 9 Oct 2009 00:28:56 -0700, Jason Thorpe 
> <thorpej%shagadelic.org@localhost>
> wrote:
>>  The
>> main intent of pool_cache_invalidate() is to nuke any cached constructed
>> copies of an object if the constructed form were to change for some
> reason.
>>  If per-CPU cached copies are not included in that, then a subsequent
>> allocation could return an incorrectly-constructed object, leading to
>> errant behavior.
> 
> - pool_cache(9) does not state that:
> 
> """
> Destruct and release all objects in the global cache.  Per-CPU caches
will
> not be invalidated by this call, meaning that it is still possible to
> allocate "stale" items from the cache.  If relevant, the user must check
> for this condition when allocating items.
> """

s/does not/does/

-- 
Jean-Yves Migeon
jeanyves.migeon%free.fr@localhost