linux-kernel - Re: [patch 1/8] slab: introduce kzfree()

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: <1234885876.11511.3.camel@penberg-laptop>
Date:	Tue, 17 Feb 2009 17:51:16 +0200
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	Christoph Lameter <cl@...ux-foundation.org>
Cc:	Johannes Weiner <hannes@...xchg.org>,
	Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org, Matt Mackall <mpm@...enic.com>,
	Nick Piggin <npiggin@...e.de>
Subject: Re: [patch 1/8] slab: introduce kzfree()

On Tue, 2009-02-17 at 10:08 -0500, Christoph Lameter wrote:
> Why would you want to zero an object on release? Is this for security?
> 
> Please give us some rationale for this. Do we need free on zero now for
> all allocators?

All the call-sites zero out before kfree() for security reasons. But
yeah, we should put that in the patch description as well.

Johannes, I suppose it would make sense to resend the series to Andrew
with all the updates?

			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/