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: Wed, 13 Apr 2016 00:29:46 -0700 From: tip-bot for Davidlohr Bueso <tipbot@...or.com> To: linux-tip-commits@...r.kernel.org Cc: peterz@...radead.org, akpm@...ux-foundation.org, hpa@...or.com, dave@...olabs.net, tglx@...utronix.de, torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org, dbueso@...e.de, mingo@...nel.org, paulmck@...ux.vnet.ibm.com Subject: [tip:locking/core] locking/Documentation: Mention smp_cond_acquire() Commit-ID: 787df6383caa1338a4f6640d71917bc2d8c068b1 Gitweb: http://git.kernel.org/tip/787df6383caa1338a4f6640d71917bc2d8c068b1 Author: Davidlohr Bueso <dave@...olabs.net> AuthorDate: Tue, 12 Apr 2016 08:52:55 -0700 Committer: Ingo Molnar <mingo@...nel.org> CommitDate: Wed, 13 Apr 2016 08:52:23 +0200 locking/Documentation: Mention smp_cond_acquire() ... do this next to smp_load_acquire() when first mentioning ACQUIRE. While this call is briefly explained and control dependencies are mentioned later, it does not hurt the reader. Signed-off-by: Davidlohr Bueso <dbueso@...e.de> Signed-off-by: Paul E. McKenney <paulmck@...ux.vnet.ibm.com> Cc: Andrew Morton <akpm@...ux-foundation.org> Cc: Davidlohr Bueso <dave@...olabs.net> Cc: Linus Torvalds <torvalds@...ux-foundation.org> Cc: Peter Zijlstra <peterz@...radead.org> Cc: Thomas Gleixner <tglx@...utronix.de> Cc: bobby.prani@...il.com Cc: dhowells@...hat.com Cc: dipankar@...ibm.com Cc: dvhart@...ux.intel.com Cc: edumazet@...gle.com Cc: fweisbec@...il.com Cc: jiangshanlai@...il.com Cc: josh@...htriplett.org Cc: mathieu.desnoyers@...icios.com Cc: oleg@...hat.com Cc: rostedt@...dmis.org Link: http://lkml.kernel.org/r/1460476375-27803-7-git-send-email-paulmck@linux.vnet.ibm.com Signed-off-by: Ingo Molnar <mingo@...nel.org> --- Documentation/memory-barriers.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/Documentation/memory-barriers.txt b/Documentation/memory-barriers.txt index 7133626..a9454b1 100644 --- a/Documentation/memory-barriers.txt +++ b/Documentation/memory-barriers.txt @@ -431,8 +431,9 @@ And a couple of implicit varieties: This acts as a one-way permeable barrier. It guarantees that all memory operations after the ACQUIRE operation will appear to happen after the ACQUIRE operation with respect to the other components of the system. - ACQUIRE operations include LOCK operations and smp_load_acquire() - operations. + ACQUIRE operations include LOCK operations and both smp_load_acquire() + and smp_cond_acquire() operations. The later builds the necessary ACQUIRE + semantics from relying on a control dependency and smp_rmb(). Memory operations that occur before an ACQUIRE operation may appear to happen after it completes.
Powered by blists - more mailing lists