linux-kernel - Re: SLUB: Return ZERO_SIZE

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, 4 Jun 2007 20:02:09 +0300
From:	"Pekka Enberg" <penberg@...helsinki.fi>
To:	"Roland Dreier" <rdreier@...co.com>
Cc:	"Linus Torvalds" <torvalds@...ux-foundation.org>,
	"Christoph Lameter" <clameter@....com>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, jeremy@...p.org
Subject: Re: SLUB: Return ZERO_SIZE_PTR for kmalloc(0)

On 6/4/07, Roland Dreier <rdreier@...co.com> wrote:
> No, because as was mentioned earlier in the thread, we want code to be
> able to handle 0-sized allocations without special cases.  The goal is
> that code like
>
>         buf = kmalloc(nobj * obj_size);
>         if (buf == NULL)
>                 return -ENOMEM;
>
> should work fine if nobj happens to be 0.  But we do want to get an
> oops if the code actually tries to read or write *buf.

Aah, missed that part of the discussion. Sorry for the noise ;-)
-
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/