linux-kernel - Re: Has slab ctor operation changed? -- was [PATCH 1/1] afs: afs_alloc_inode: use kmem_cache

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]

Message-ID: <alpine.DEB.2.10.1402241347050.20839@nuc>
Date:	Mon, 24 Feb 2014 13:52:07 -0600 (CST)
From:	Christoph Lameter <cl@...ux.com>
To:	David Howells <dhowells@...hat.com>
cc:	Fabian Frederick <fabf@...net.be>, linux-kernel@...r.kernel.org,
	akpm <akpm@...ux-foundation.org>
Subject: Re: Has slab ctor operation changed? -- was [PATCH 1/1] afs:
 afs_alloc_inode: use kmem_cache_zalloc

On Thu, 20 Feb 2014, David Howells wrote:

> Of course, it's possible that the slab allocator no longer works like this...

They still work like that (aside from SLOB that calls the ctor on each
alloc but that also has never changed).

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