linux-kernel - Re: [PATCH v2 2/2] SLUB: Mark merged slab caches in /proc/slabinfo

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 14 Sep 2010 23:11:13 +0300
From:	Pekka Enberg <penberg@...nel.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	David Rientjes <rientjes@...gle.com>, linux-kernel@...r.kernel.org,
	Christoph Lameter <cl@...ux.com>
Subject: Re: [PATCH v2 2/2] SLUB: Mark merged slab caches in /proc/slabinfo

  On 14.9.2010 23.05, Linus Torvalds wrote:
> On Tue, Sep 14, 2010 at 1:00 PM, David Rientjes<rientjes@...gle.com>  wrote:
>> I can understand how it's confusing that only the first slab cache name is
>> being emitted, and I think that can be changed, but this shows way too
>> much information that is already available when CONFIG_SLUB_DEBUG is used
>> via the sysfs interface.
> Umm. Not in any readable form, it isn't.
>
> The cause for this is that I made a bug-report about the wrong slab
> info, with me claiming 400+ thousand entries (taking up 10M of memory)
> for a slub cache that turned out to be entirely innocent.
>
> That's what /proc/slabinfo said, and quite frankly, /proc/slabinfo was
> simply _lying_. It gave very misleading output.
>
> In my not-so-humble opinion, either the merging needs to go away
> entirely, or the misleading output needs to be fixed. The whole (and
> _only_) reason for /proc/slabinfo is to show where memory is being
> used, so if that file is misleading, then it's worse than useless.
> Pointing to some other /sys file as having more information doesn't
> change that in the least.
Are you happy with the patch? The output is indeed tad bit unreadable. 
Maybe we should just limit the number of printed out names to two or three?

             Pekka
--
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/