linux-kernel - Re: [PATCH RFC v2] slab: introduce kmalloc

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:	Thu, 9 Feb 2012 15:08:56 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	David Rientjes <rientjes@...gle.com>
Cc:	Xi Wang <xi.wang@...il.com>, Jens Axboe <axboe@...nel.dk>,
	Pekka Enberg <penberg@...nel.org>,
	Dan Carpenter <dan.carpenter@...cle.com>,
	linux-kernel@...r.kernel.org, Christoph Lameter <cl@...ux.com>,
	Matt Mackall <mpm@...enic.com>
Subject: Re: [PATCH RFC v2] slab: introduce kmalloc_array

On Thu, 9 Feb 2012 14:42:49 -0800 (PST)
David Rientjes <rientjes@...gle.com> wrote:

> On Thu, 9 Feb 2012, Xi Wang wrote:
> 
> > This patch introduces a kmalloc_array() wrapper that performs integer
> > overflow checking without zeroing the memory.
> > 
> > Suggested-by: Andrew Morton <akpm@...ux-foundation.org>
> > Suggested-by: Jens Axboe <axboe@...nel.dk>
> > Signed-off-by: Xi Wang <xi.wang@...il.com>
> 
> Acked-by: David Rientjes <rientjes@...gle.com>
> 
> assuming there's at least one new user or one existing user that can be 
> modified to use the new interface and this won't just sit around not being 
> used.

The need is there - I've whined about the absence of kmalloc_array()
maybe 3 times in the past year.

Often kcalloc() is suitable - quite a lot of arrays which are sized
based on a userspace-provided dimension are also zeroed out.  For some
reason.

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