diff options
| author | Catalin Marinas <catalin.marinas@arm.com> | 2008-11-21 12:56:22 +0000 |
|---|---|---|
| committer | Pekka Enberg <penberg@cs.helsinki.fi> | 2008-11-26 16:48:47 +0200 |
| commit | 249da166582801648432d0198be9407fb5ccf9f5 (patch) | |
| tree | 15b101e9dec5be04fe080197ba489af44e098883 | |
| parent | ed313489badef16d700f5a3be50e8fd8f8294bc8 (diff) | |
slab: Update the kmem_cache_create documentation regarding the name parameter
kmem_cache implementations like slub are allowed to merge multiple
caches but only the initial name is preserved. Therefore,
kmem_cache_name() is not guaranteed to return the same pointer passed to
the former function. This patch updates the documentation to make this
clearer.
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Signed-off-by: Pekka Enberg <penberg@cs.helsinki.fi>
| -rw-r--r-- | mm/slab.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/mm/slab.c b/mm/slab.c index 09187517f9d..c366e3910e8 100644 --- a/mm/slab.c +++ b/mm/slab.c @@ -2123,6 +2123,8 @@ static int __init_refok setup_cpu_cache(struct kmem_cache *cachep) * * @name must be valid until the cache is destroyed. This implies that * the module calling this has to destroy the cache before getting unloaded. + * Note that kmem_cache_name() is not guaranteed to return the same pointer, + * therefore applications must manage it themselves. * * The flags are * |