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]
Message-ID: <466573E0.8050809@gmail.com>
Date:	Tue, 05 Jun 2007 16:32:00 +0200
From:	Rene Herman <rene.herman@...il.com>
To:	"John Anthony Kazos Jr." <jakj@...-k-j.com>
CC:	Christoph Lameter <clameter@....com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Pekka Enberg <penberg@...helsinki.fi>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Jeremy Fitzhardinge <jeremy@...p.org>
Subject: Re: SLUB: Return ZERO_SIZE_PTR for kmalloc(0)

On 06/05/2007 03:58 PM, John Anthony Kazos Jr. wrote:

> So "ZERO_SIZE_OBJ_PTR" is the most correct form, and "ZERO_SIZE_PTR" is a
> convenient shortening. "ZERO_PTR" is too short and also confuses with NULL
> because NULL is a zero-value object, rather than a non-zero--value pointer to
> a zero-size object.

Like I said, I would prefer NIL of if absolutely need be NIL_PTR. NULL is a 
pointer that doesn't point anywhere valid -- NIL is a pointer that points to a 
zero sized object.

If I'd have a few small children around I'd show them the word ZERO_SIZE_PTR and 
make pictures of them bursting out in tears.

Rene.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ