linux-kernel - Re: [KJ] replacing kmalloc with kzalloc in io

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, 13 Aug 2007 10:27:07 -0700
From:	Roland Dreier <rdreier@...co.com>
To:	"Robert P. J. Day" <rpjday@...dspring.com>
Cc:	Mariusz Kozlowski <m.kozlowski@...land.pl>,
	surya.prabhakar@...ro.com, mingo@...hat.com,
	yaku@...1.kbnes.nec.co.jp, kisimoto@...1.kbnes.nec.co.jp,
	zab@...hat.com, Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [KJ] replacing kmalloc with kzalloc in io_apic.c

 > from my days submitting numerous patches of this type, i can recall
 > that in cases like the above, it's a judgment call -- use kzalloc to
 > get the zeroing, or use kcalloc to get the array-flavoured behaviour.
 > what a shame you can't have both at the same time.

kcalloc() zeros memory just like standard calloc() in userspace.

As <linux/slab.h> says:

 * kcalloc - allocate memory for an array. The memory is set to zero.
-
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/