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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 8 Oct 2014 09:10:23 +0000 From: David Laight <David.Laight@...LAB.COM> To: 'Hannes Frederic Sowa' <hannes@...essinduktion.org>, Fabian Frederick <fabf@...net.be> CC: Guenter Roeck <linux@...ck-us.net>, David Miller <davem@...emloft.net>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: RE: [PATCH 1/1 net-next] af_unix: remove NULL assignment on static From: Hannes Frederic Sowa > I think David's concern was whether if 0 == false in all situations. It > is pretty clear that static memory is initialized to 0. I'm not 100% sure about that. static pointers may be required to be initialised to NULL. If NULL isn't the 'all 0 bit pattern' then the memory would need to be initialised to a different pattern. Not that anyone is likely to implement such a system because far too much code will break. The only system I knew where 'native' NULL pointers were 'all 1s' used 0 in its C compiler. David
Powered by blists - more mailing lists