linux-kernel - Re: [PATCH] slub: operate cache name memory same to slab and slob

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sat, 20 Nov 2010 16:55:22 -0800 (PST)
From:	David Rientjes <rientjes@...gle.com>
To:	Matt Mackall <mpm@...enic.com>
cc:	b32542@...escale.com, linux-mm@...ck.org,
	Christoph Lameter <cl@...ux-foundation.org>,
	Pekka Enberg <penberg@...helsinki.fi>, tytso@....edu,
	linux-kernel@...r.kernel.org,
	Zeng Zhaoming <zengzm.kernel@...il.com>
Subject: Re: [PATCH] slub: operate cache name memory same to slab and slob

On Thu, 18 Nov 2010, Matt Mackall wrote:

> > The leak in ext4_mb_init() above is because it is using kstrdup() to 
> > allocate the string itself and then on destroy uses kmem_cache_name() to 
> > attain the slub allocator's pointer to the name, not the memory the ext4 
> > layer allocated itself.
> 
> And Pekka says:
> 
> > The kstrdup() is there because of SLUB cache merging. See commit 
> > 84c1cf62465e2fb0a692620dcfeb52323ab03d48 ("SLUB: Fix merged slab 
> > cache names") for details.
> 
> I see. So we can either:
> 
> - force anyone using dynamically-allocated names to track their own damn
> pointer
> - implement kstrdup in the other allocators and fix all callers (the
> bulk of which use static names!)
> - eliminate dynamically-allocated names (mostly useless when we start
> merging slabs!)
> - add an indirection layer for slub that holds the unmerged details
> - stop pretending we track slab names and show only generic names based
> on size in /proc
> 

I agree that we should force each user to track its own memory, and this 
is really what the issue is about (it doesn't matter if that memory is the 
cache's name).  This particular issue is an ext4 memory leak and not the 
responsibility of any allocator.

> kmem_cache_name() is also a highly suspect function in a
> post-merged-slabs kernel. As ext4 is the only user in the kernel, and it
> got it wrong, perhaps it's time to rip it out.
> 

Yes, I think kmem_cache_name() should be removed since it shouldn't be 
used for anything other than the internal slabinfo/slabtop display as the 
slub allocator actually specifies in include/linux/slub_def.h.  The only 
user is ext4 to track this dynamically allocated pointer, so we can 
eliminate it if we leave it to track its own memory allocations (a slab 
allocator shouldn't be carrying a metadata payload).
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/