| 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
| ||
|
Message-ID: <6598f8b90905021547v42564e64t224091a6adb15104@mail.gmail.com> Date: Sat, 2 May 2009 17:47:07 -0500 From: John Sheu <john.sheu@...il.com> To: linux-kernel@...r.kernel.org Subject: x86: atomic.h memory clobbers Looking at include/asm-i386/atomic.h, is there any particular reason why "memory" is in the clobber list for, say, atomic_sub_and_test, and not atomic_sub? As far as I can tell, all the possible memory operands are already in the in/out lists, and any memory-barrier concerns (if any) that happen to atomic_sub_and_test should apply equally for atomic_sub. -John Sheu -- 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