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: Thu, 02 Feb 2012 10:51:20 -0500 From: Jeff Garzik <jeff@...zik.org> To: Linus Torvalds <torvalds@...ux-foundation.org> CC: Jeff Law <law@...hat.com>, David Miller <davem@...emloft.net>, matz@...e.de, jkosina@...e.cz, walters@...bum.org, jack@...e.cz, linux-kernel@...r.kernel.org, linux-ia64@...r.kernel.org, dsterba@...e.cz, ptesarik@...e.cz, rguenther@...e.de, gcc@....gnu.org Subject: Re: Memory corruption due to word sharing On 02/01/2012 02:09 PM, Linus Torvalds wrote: > We have a lot of code, there's still a lot of situations left where > bitfields are just really convenient. Or even just s/convenient/ingrained habit/ As much as I try to avoid bitfields, engineers writing vendor drivers love to lay out their hardware structures using bitfields, leading to such crapola as #ifdef little endian a bunch of bitfields, LE arrangement #else bitfields, now in BE arrangement #endif This crops up again and again in drivers :/ Jeff -- 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