linux-kernel - Re: [PATCH] module: avoid call vmalloc if init size is zero

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] [day] [month] [year] [list]

Message-ID: <878vkpmxqt.fsf@rustcorp.com.au>
Date:	Mon, 30 Jan 2012 18:24:18 +1030
From:	Rusty Russell <rusty@...tcorp.com.au>
To:	Dmitry Antipov <dmitry.antipov@...aro.org>
Cc:	linux-kernel@...r.kernel.org, linaro-dev@...ts.linaro.org
Subject: Re: [PATCH] module: avoid call vmalloc if init size is zero

On Mon, 30 Jan 2012 11:28:12 +0400, Dmitry Antipov <dmitry.antipov@...aro.org> wrote:
> On 01/27/2012 03:21 PM, Rusty Russell wrote:
> 
> > Please fix __vmalloc_node_range() instead to return ZERO_SIZE_PTR.
> > And of course, vfree() to use ZERO_OR_NULL_PTR().
> 
> For the convenience and uniformity, should {alloc,free}_percpu() be
> also modified in that way?

Yep!

Thanks,
Rusty.
--
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/