diff options
| author | Joonsoo Kim <iamjoonsoo.kim@lge.com> | 2013-10-30 19:04:00 +0900 |
|---|---|---|
| committer | Pekka Enberg <penberg@iki.fi> | 2013-10-30 14:08:52 +0200 |
| commit | 0172f779e4314639a8ed440082cfe9e3450954e8 (patch) | |
| tree | 48115e3a18009a192e124fca81454778ef6b35ef | |
| parent | e7444d9b7d49898a667074122bed2dcedf349305 (diff) | |
slab: fix to calm down kmemleak warning
After using struct page as slab management, we should not call
kmemleak_scan_area(), since struct page isn't the tracking object of
kmemleak. Without this patch and if CONFIG_DEBUG_KMEMLEAK is enabled,
so many kmemleak warnings are printed.
Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Signed-off-by: Pekka Enberg <penberg@iki.fi>
| -rw-r--r-- | mm/slab.c | 8 |
1 files changed, 0 insertions, 8 deletions
diff --git a/mm/slab.c b/mm/slab.c index af2db76e1f5a..a8a93497d7d6 100644 --- a/mm/slab.c +++ b/mm/slab.c @@ -2531,14 +2531,6 @@ static struct freelist *alloc_slabmgmt(struct kmem_cache *cachep, /* Slab management obj is off-slab. */ freelist = kmem_cache_alloc_node(cachep->freelist_cache, local_flags, nodeid); - /* - * If the first object in the slab is leaked (it's allocated - * but no one has a reference to it), we want to make sure - * kmemleak does not treat the ->s_mem pointer as a reference - * to the object. Otherwise we will not report the leak. - */ - kmemleak_scan_area(&page->lru, sizeof(struct list_head), - local_flags); if (!freelist) return NULL; } else { |