linux-kernel - [PATCH] Documentation/memory-barriers.txt: match table to its comment followed

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>] [thread-next>] [day] [month] [year] [list]

Message-ID: <5417FA0F.1030403@huawei.com>
Date:	Tue, 16 Sep 2014 16:51:27 +0800
From:	Yao Dongdong <yaodongdong@...wei.com>
To:	Randy Dunlap <rdunlap@...radead.org>
CC:	<linux-doc@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: [PATCH] Documentation/memory-barriers.txt: match table to its comment
 followed

The table shows CPU2's sequence of events as "x = B; y = A;", but its comment followed
described as "x = A; y = B;".

Signed-off-by: Yao Dongdong <yaodongdong@...wei.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 a4de88f..9a46bbe 100644
--- a/Documentation/memory-barriers.txt
+++ b/Documentation/memory-barriers.txt
@@ -115,8 +115,8 @@ For example, consider the following sequence of events:
        CPU 1           CPU 2
        =============== ===============
        { A == 1; B == 2 }
-       A = 3;          x = B;
-       B = 4;          y = A;
+       A = 3;          x = A;
+       B = 4;          y = B;

 The set of accesses as seen by the memory system in the middle can be arranged
 in 24 different combinations:
--
1.8.0.1

--
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/