linux-kernel - [PATCH] Documentation/memory-barriers: fix wrong comment in example

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 for Android: free password hash cracker in your pocket

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

Message-Id: <1455948068-14221-1-git-send-email-sj38.park@gmail.com>
Date:	Sat, 20 Feb 2016 15:01:08 +0900
From:	SeongJae Park <sj38.park@...il.com>
To:	corbet@....net, dhowells@...hat.com, paulmck@...ux.vnet.ibm.com
Cc:	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
	SeongJae Park <sj38.park@...il.com>
Subject: [PATCH] Documentation/memory-barriers: fix wrong comment in example

There is wrong comment in example for compiler store omit behavior.  It
shows example of the problem and than problem solved version code.
However, the comment in the solved version is still same with not solved
version.  Fix the wrong statement with this commit.

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 061ff29..b4754c7 100644
--- a/Documentation/memory-barriers.txt
+++ b/Documentation/memory-barriers.txt
@@ -1471,7 +1471,7 @@ of optimizations:
      wrong guess:
 
 	WRITE_ONCE(a, 0);
-	/* Code that does not store to variable a. */
+	/* Code that does store to variable a. */
 	WRITE_ONCE(a, 0);
 
  (*) The compiler is within its rights to reorder memory accesses unless
-- 
1.9.1