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: Fri, 18 Jul 2014 09:23:24 -0500 (CDT) From: Christoph Lameter <cl@...two.org> To: Pranith Kumar <bobby.prani@...il.com> cc: rdunlap@...radead.org, linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH v2 1/1] doc: Add remote CPU access details and others to this_cpu_ops.txt On Thu, 17 Jul 2014, Pranith Kumar wrote: > > then we have on x86 a increment operation with locked semantics racing > > with an unlocked one on the same cacheline. > OK, I will add this as a warning in the documentation. Thanks! Note that I have not been able to get beyond a bad feeling. Looked up various sources of information about how the lock prefix works. Still I am not sure if this works or not. -- 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