| 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, 9 Aug 2007 17:30:16 +0200 From: Arnd Bergmann <arnd@...db.de> To: Chris Snook <csnook@...hat.com> Cc: linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org, torvalds@...ux-foundation.org, netdev@...r.kernel.org, akpm@...ux-foundation.org, ak@...e.de, heiko.carstens@...ibm.com, davem@...emloft.net, schwidefsky@...ibm.com, wensong@...ux-vs.org, horms@...ge.net.au, wjiang@...ilience.com, cfriesen@...tel.com, zlynx@....org, rpjday@...dspring.com, jesper.juhl@...il.com Subject: Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures On Thursday 09 August 2007, Chris Snook wrote: > a) chicken and egg: asm-generic/atomic.h depends on definitions in asm/atomic.h Ok, I see. > If you can find a way to reshuffle the code and make it simpler, I personally am > all for it. I'm skeptical that you'll get much to show for the effort. I guess it could be done using more macros or new headers, but I don't see a way that would actually improve the situation. > b) The definitions aren't precisely identical between all architectures, so it > would be a mess of special cases, which gets us right back to where we are now. Why are they not identical? Anything beyond the 32/64 bit difference should be the same afaics, or it might cause more bugs. Arnd <>< - 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