linux-kernel - Re: [PATCH] some kmalloc/memset ->kzalloc (tree wide)

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0707061052570.30575@schroedinger.engr.sgi.com>
Date:	Fri, 6 Jul 2007 10:54:29 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	Peter Zijlstra <peterz@...radead.org>
cc:	Yoann Padioleau <padator@...adoo.fr>,
	kernel-janitors@...ts.osdl.org, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] some kmalloc/memset ->kzalloc (tree wide)

On Fri, 6 Jul 2007, Peter Zijlstra wrote:

> On Fri, 2007-07-06 at 18:51 +0200, Yoann Padioleau wrote:
> > Transform some calls to kmalloc/memset to a single kzalloc (or
> > kcalloc).
> > 
> 
> Christoph, what is the plan wrt GFP_ZERO?

Its going in AFAIK. Need to resort my patches and then I will push it 
back.

kzalloc will continue to exist as a shorthand notation. So no problem with 
continuing the conversion. kmalloc with GFP_ZERO may be more advantageous 
in allocator type functionality where the caller may want to specify if 
the allocated memory should be zeroed or not.

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