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 13:00:02 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	Pekka Enberg <penberg@...nel.org>
cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	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 Tue, 14 Sep 2010, Pekka Enberg wrote:

> SLUB uses the name of the first slab cache for all merged slab caches. To make
> the output of /proc/slabinfo more obvious, append the name of each merged slab
> cache to s->name.
> 
> An example output of /proc/slabinfo with this patch looks like this:
> 
>   kmalloc-8192         544    544   8192    4    8 : tunables    0
>   kmalloc-4096+names_cache+biovec-256+sgpool-128+ecryptfs_headers
>   kmalloc-2048+biovec-128+sgpool-64    400    416   2048   16    8
>   kmalloc-1024+biovec-64+sgpool-32    436    496   1024   16    4 :
>   kmalloc-512+task_xstate+skbuff_fclone_cache+sgpool-16   1060   10
>   kmalloc-256+mnt_cache+skbuff_head_cache+biovec-16+sgpool-8+arp_   [ snip ]
>   kmalloc-128+pid+bip-1+eventpoll_epi+request_sock_TCP+ip_mrt_cac
>   kmalloc-64+fs_cache+biovec-4+blkdev_ioc+inet_peer_cache+tcp_bin
>   kmalloc-32+ip_fib_alias+dnotify_struct+inotify_event_private_da
>   kmalloc-16+biovec-1+ecryptfs_file_cache+dm_rq_clone_bio_info+dm
>   kmalloc-8           5119   5120      8  512    1 : tunables    0
>   kmalloc-192+cred_jar+key_jar+filp+bip-4+bio-0+request_sock_TCPv
>   kmalloc-96           924   1008     96   42    1 : tunables    0
>   kmem_cache_node      128    128     64   64    1 : tunables    0
> 

I really don't like this.

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.

CONFIG_SLUB_DEBUG is the default configuration for all users and is 
required for CONFIG_SLABINFO when using slub.  It softlinks merged caches 
together so that it's very simple to determine their relationship.

There's also nothing preventing a name from already including a '+' 
itself.

I think it would be better to use the unique id of each slab cache when 
emitting this information, perhaps suffixed with a count of the number of 
caches merged such as ":t-0000008(3)".
--
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/