linux-kernel - [PATCH] memory-barriers: Make sentence more clear.

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:   Mon, 19 Feb 2018 18:00:30 +0200
From:   Nikolay Borisov <nborisov@...e.com>
To:     paulmck@...ux.vnet.ibm.com
Cc:     peterz@...radead.org, dbueso@...e.com,
        linux-kernel@...r.kernel.org, Nikolay Borisov <nborisov@...e.com>
Subject: [PATCH] memory-barriers: Make sentence more clear.

Rewrite the final sentence of data dependency memory barrier to express
the 'after' relationship in simpler words.

Signed-off-by: Nikolay Borisov <nborisov@...e.com>
---
 Documentation/memory-barriers.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/memory-barriers.txt b/Documentation/memory-barriers.txt
index a863009849a3..d7bc0132ef5a 100644
--- a/Documentation/memory-barriers.txt
+++ b/Documentation/memory-barriers.txt
@@ -399,8 +399,8 @@ VARIETIES OF MEMORY BARRIER
      where two loads are performed such that the second depends on the result
      of the first (eg: the first load retrieves the address to which the second
      load will be directed), a data dependency barrier would be required to
-     make sure that the target of the second load is updated before the address
-     obtained by the first load is accessed.
+     make sure that the target of the second load is updated to the value
+     obtained by the first load.
 
      A data dependency barrier is a partial ordering on interdependent loads
      only; it is not required to have any effect on stores, independent loads
-- 
2.7.4