linux-kernel - [PATCH] tools/memory-model: Fix litmus-tests's file names.

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]
Message-ID: <20241209150044.766-1-egyszeregy@freemail.hu>
Date: Mon,  9 Dec 2024 16:00:44 +0100
From: egyszeregy@...email.hu
To: stern@...land.harvard.edu,
	parri.andrea@...il.com,
	will@...nel.org,
	peterz@...radead.org,
	boqun.feng@...il.com,
	npiggin@...il.com,
	dhowells@...hat.com,
	j.alglave@....ac.uk,
	luc.maranget@...ia.fr,
	paulmck@...nel.org,
	akiyks@...il.com,
	dlustig@...dia.com,
	joel@...lfernandes.org,
	linux-kernel@...r.kernel.org,
	linux-arch@...r.kernel.org,
	lkmm@...ts.linux.dev
Cc: Benjamin Szőke <egyszeregy@...email.hu>
Subject: [PATCH] tools/memory-model: Fix litmus-tests's file names.

From: Benjamin Szőke <egyszeregy@...email.hu>

Makes a greater Hamming distance for name of Z6.0+pooncelock* files.

Signed-off-by: Benjamin Szőke <egyszeregy@...email.hu>
---
 tools/memory-model/Documentation/locking.txt                  | 4 ++--
 tools/memory-model/Documentation/recipes.txt                  | 4 ++--
 tools/memory-model/litmus-tests/README                        | 4 ++--
 ...ncelock+pooncelock+smp_mb__after_spinlock+pombonce.litmus} | 0
 ...s => Z6.0+pooncelock+pooncelock+spin_lock+pombonce.litmus} | 0
 5 files changed, 6 insertions(+), 6 deletions(-)
 rename tools/memory-model/litmus-tests/{Z6.0+pooncelock+poonceLock+pombonce.litmus => Z6.0+pooncelock+pooncelock+smp_mb__after_spinlock+pombonce.litmus} (100%)
 rename tools/memory-model/litmus-tests/{Z6.0+pooncelock+pooncelock+pombonce.litmus => Z6.0+pooncelock+pooncelock+spin_lock+pombonce.litmus} (100%)

diff --git a/tools/memory-model/Documentation/locking.txt b/tools/memory-model/Documentation/locking.txt
index 65c898c64a93..c213aa4a8668 100644
--- a/tools/memory-model/Documentation/locking.txt
+++ b/tools/memory-model/Documentation/locking.txt
@@ -151,7 +151,7 @@ Ordering Provided by a Lock to CPUs Not Holding That Lock
 It is not necessarily the case that accesses ordered by locking will be
 seen as ordered by CPUs not holding that lock.  Consider this example:
 
-	/* See Z6.0+pooncelock+pooncelock+pombonce.litmus. */
+	/* See Z6.0+pooncelock+pooncelock+spin_lock+pombonce.litmus. */
 	void CPU0(void)
 	{
 		spin_lock(&mylock);
@@ -184,7 +184,7 @@ ordering properties.
 Ordering can be extended to CPUs not holding the lock by careful use
 of smp_mb__after_spinlock():
 
-	/* See Z6.0+pooncelock+poonceLock+pombonce.litmus. */
+	/* See Z6.0+pooncelock+pooncelock+smp_mb__after_spinlock+pombonce.litmus. */
 	void CPU0(void)
 	{
 		spin_lock(&mylock);
diff --git a/tools/memory-model/Documentation/recipes.txt b/tools/memory-model/Documentation/recipes.txt
index 03f58b11c252..3c55146e8fe4 100644
--- a/tools/memory-model/Documentation/recipes.txt
+++ b/tools/memory-model/Documentation/recipes.txt
@@ -126,7 +126,7 @@ However, it is not necessarily the case that accesses ordered by
 locking will be seen as ordered by CPUs not holding that lock.
 Consider this example:
 
-	/* See Z6.0+pooncelock+pooncelock+pombonce.litmus. */
+	/* See Z6.0+pooncelock+pooncelock+spin_lock+pombonce.litmus. */
 	void CPU0(void)
 	{
 		spin_lock(&mylock);
@@ -159,7 +159,7 @@ lock's ordering properties.
 Ordering can be extended to CPUs not holding the lock by careful use
 of smp_mb__after_spinlock():
 
-	/* See Z6.0+pooncelock+poonceLock+pombonce.litmus. */
+	/* See Z6.0+pooncelock+pooncelock+smp_mb__after_spinlock+pombonce.litmus. */
 	void CPU0(void)
 	{
 		spin_lock(&mylock);
diff --git a/tools/memory-model/litmus-tests/README b/tools/memory-model/litmus-tests/README
index d311a0ff1ae6..82e5b58b8ac6 100644
--- a/tools/memory-model/litmus-tests/README
+++ b/tools/memory-model/litmus-tests/README
@@ -144,12 +144,12 @@ WRC+pooncerelease+fencermbonceonce+Once.litmus
 	The second is forbidden because smp_store_release() is
 	A-cumulative in LKMM.
 
-Z6.0+pooncelock+pooncelock+pombonce.litmus
+Z6.0+pooncelock+pooncelock+spin_lock+pombonce.litmus
 	Is the ordering provided by a spin_unlock() and a subsequent
 	spin_lock() sufficient to make ordering apparent to accesses
 	by a process not holding the lock?
 
-Z6.0+pooncelock+poonceLock+pombonce.litmus
+Z6.0+pooncelock+pooncelock+smp_mb__after_spinlock+pombonce.litmus
 	As above, but with smp_mb__after_spinlock() immediately
 	following the spin_lock().
 
diff --git a/tools/memory-model/litmus-tests/Z6.0+pooncelock+poonceLock+pombonce.litmus b/tools/memory-model/litmus-tests/Z6.0+pooncelock+pooncelock+smp_mb__after_spinlock+pombonce.litmus
similarity index 100%
rename from tools/memory-model/litmus-tests/Z6.0+pooncelock+poonceLock+pombonce.litmus
rename to tools/memory-model/litmus-tests/Z6.0+pooncelock+pooncelock+smp_mb__after_spinlock+pombonce.litmus
diff --git a/tools/memory-model/litmus-tests/Z6.0+pooncelock+pooncelock+pombonce.litmus b/tools/memory-model/litmus-tests/Z6.0+pooncelock+pooncelock+spin_lock+pombonce.litmus
similarity index 100%
rename from tools/memory-model/litmus-tests/Z6.0+pooncelock+pooncelock+pombonce.litmus
rename to tools/memory-model/litmus-tests/Z6.0+pooncelock+pooncelock+spin_lock+pombonce.litmus
-- 
2.43.5