linux-kernel - Re: [PATCH] slab+slob: dup name string

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]

Message-ID: <4FBCD328.6060406@parallels.com>
Date:	Wed, 23 May 2012 16:08:08 +0400
From:	Glauber Costa <glommer@...allels.com>
To:	James Bottomley <James.Bottomley@...senPartnership.com>
CC:	David Rientjes <rientjes@...gle.com>,
	Christoph Lameter <cl@...ux.com>,
	<linux-kernel@...r.kernel.org>, <cgroups@...r.kernel.org>,
	<linux-mm@...ck.org>, Pekka Enberg <penberg@...helsinki.fi>
Subject: Re: [PATCH] slab+slob: dup name string

On 05/23/2012 03:46 PM, James Bottomley wrote:
>> We can't predict how slab will be extended in the future and this affects
>> >  anything created before g_cpucache_cpu<= EARLY.  This would introduce the
>> >  first problem with destroying such caches and is unnecessary if a
>> >  workaround exists.
> These problems seem to indicate that the slab behaviour: expecting the
> string to exist for the lifetime of the cache so there's no need to copy
> it might be better.
>
> This must be the behaviour all users of kmem_cache_create() expect
> anyway, since all enterprise distributions use slab and they're not
> getting bugs reported in this area.
>
> So, why not simply patch slab to rely on the string lifetime being the
> cache lifetime (or beyond) and therefore not having it take a copy?
>
You mean patch slub? slub is the one that takes a copy currently.

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