Update the kmem_cache_create documentation regarding the name parameter
PATCH 1/1 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 <[email protected]>
Cc Pekka Enberg <[email protected]>
--- mm/slab.c | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-)
mm/slab.c +2 -0
@@ -2124,6 +2124,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 *
Pekka Enberg
AppliedHi Catalin,
Quoted 8 lines · Catalin Marinas
kmem_cacheimplementations 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 <[email protected]>Cc Pekka Enberg <[email protected]>
Applied, thanks!
Quoted 18 lines
--- mm/slab.c | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-)mm/slab.c +2
-0@@ -2124,6 +2124,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 *