linux-kernel - Re: [RFC/PATCH 2/2] slub: Don't share struct kmem

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:	Mon, 25 Apr 2011 14:09:26 -0500 (CDT)
From:	Christoph Lameter <cl@...ux.com>
To:	Pekka Enberg <penberg@...nel.org>
cc:	linux-kernel@...r.kernel.org, David Rientjes <rientjes@...gle.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [RFC/PATCH 2/2] slub: Don't share struct kmem_cache for shared
 caches

On Mon, 25 Apr 2011, Pekka Enberg wrote:

> This patch changes the slab cache sharing in SLUB to only share 'struct
> kmem_cpu_cache' which contains the actual list of slabs and object freelists.
> We no longer share 'struct kmem_cache' between merged caches so /proc/slabinfo
> statistics work as expected:

I am a bit confused. Struct kmem_cache contains per slab
allocation information and all pages have pointers to struct kmem_cache.

So we have pages now on the kmem_cache_cpu list with varying kmem_cache
pointers? How do we figure out which cache a page belongs to? It seems
that a page from one cache can be freed to the freelists of another.

Does this even run right with the debugging enabled?

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