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: Mon, 13 Jul 2015 15:11:43 +0200 From: Peter Zijlstra <peterz@...radead.org> To: Will Deacon <will.deacon@....com> Cc: linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org, Benjamin Herrenschmidt <benh@...nel.crashing.org>, Paul McKenney <paulmck@...ux.vnet.ibm.com> Subject: Re: [RFC PATCH v2] memory-barriers: remove smp_mb__after_unlock_lock() On Mon, Jul 13, 2015 at 01:15:04PM +0100, Will Deacon wrote: > smp_mb__after_unlock_lock is used to promote an UNLOCK + LOCK sequence > into a full memory barrier. > > However: > - The barrier only applies to UNLOCK + LOCK, not general > RELEASE + ACQUIRE operations No it does too; note that on ppc both acquire and release use lwsync and two lwsyncs do not make a sync. -- 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