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
| ||
|
Date: Wed, 15 Aug 2007 10:37:52 +0200 From: Rene Herman <rene.herman@...il.com> To: Jan Engelhardt <jengelh@...putergmbh.de> CC: Jason Uhlenkott <jasonuhl@...onuhl.org>, Arjan van de Ven <arjan@...radead.org>, Tim Bird <tim.bird@...sony.com>, linux kernel <linux-kernel@...r.kernel.org> Subject: Re: kfree(0) - ok? On 08/15/2007 09:28 AM, Jan Engelhardt wrote: > On Aug 14 2007 16:21, Jason Uhlenkott wrote: >> On Tue, Aug 14, 2007 at 15:55:48 -0700, Arjan van de Ven wrote: >>> NULL is not 0 though. >> It is. Its representation isn't guaranteed to be all-bits-zero, > > C guarantees that. C guarantees what? If you're disagreeing with Jason -- he's right. >> but the constant value 0 when used in pointer context is always a >> null pointer (and in fact the standard requires that NULL be >> #defined as 0 or a cast thereof). 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