linux-kernel - [PATCH v5 1/2] Doc/memory-barriers: Fix a typo of example result

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

Message-Id: <1469063458-6573-2-git-send-email-sj38.park@gmail.com>
Date:	Thu, 21 Jul 2016 10:10:57 +0900
From:	SeongJae Park <sj38.park@...il.com>
To:	byungchul.park@....com, paulmck@...ux.vnet.ibm.com, corbet@....net,
	mingo@...nel.org
Cc:	dhowells@...hat.com, minchan@...nel.org,
	linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
	SeongJae Park <sj38.park@...il.com>
Subject: [PATCH v5 1/2] Doc/memory-barriers: Fix a typo of example result

An example result for data dependent write has a typo.  This commit
fixes the wrong typo.

Signed-off-by: SeongJae Park <sj38.park@...il.com>
---
 Documentation/memory-barriers.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/memory-barriers.txt b/Documentation/memory-barriers.txt
index 19c8eb6..ba818ec 100644
--- a/Documentation/memory-barriers.txt
+++ b/Documentation/memory-barriers.txt
@@ -609,7 +609,7 @@ A data-dependency barrier must also order against dependent writes:
 The data-dependency barrier must order the read into Q with the store
 into *Q.  This prohibits this outcome:
 
-	(Q == B) && (B == 4)
+	(Q == &B) && (B == 4)
 
 Please note that this pattern should be rare.  After all, the whole point
 of dependency ordering is to -prevent- writes to the data structure, along
-- 
1.9.1