linux-kernel - Re: [PATCH] tools/memory-model: Fix litmus-tests's file names for case-insensitive filesystem.

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: <e3a5aa0a-2c8b-4679-9344-64135df63fe1@paulmck-laptop>
Date: Tue, 12 Nov 2024 13:53:04 -0800
From: "Paul E. McKenney" <paulmck@...nel.org>
To: Alan Stern <stern@...land.harvard.edu>
Cc: Szőke Benjamin <egyszeregy@...email.hu>,
	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, akiyks@...il.com,
	dlustig@...dia.com, joel@...lfernandes.org,
	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
	lkmm@...ts.linux.dev, torvalds@...ux-foundation.org
Subject: Re: [PATCH] tools/memory-model: Fix litmus-tests's file names for
 case-insensitive filesystem.

On Tue, Nov 12, 2024 at 03:20:00PM -0500, Alan Stern wrote:
> On Tue, Nov 12, 2024 at 10:26:37AM -0800, Paul E. McKenney wrote:
> > We do have a rule for the filenames in that directory that most of
> > them follow (I am looking at *you*, "dep+plain.litmus"!).  So we have
> > a few options:
> > 
> > 1.	Status quo.  (How boring!!!)
> > 
> > 2.	Come up with a better rule mapping the litmus-test file
> > 	contents to the filename, and rename things to follow that rule.
> > 	(Holy bikeshedding, Batman!)
> > 
> > 3.	Keep it simple and keep the current rule, but make the
> > 	combination of spin_lock() and smp_mb__after_spinlock()
> > 	have a greater Hamming distance from "lock".  Szőke's
> > 	patch changed only one of the filenames containing "Lock".
> > 	(Bikeshedding, but narrower scope.)
> > 
> > 4.	One of the above, but bring the litmus tests not following
> > 	the rule into compliance.
> > 
> > 5.	Give up on the idea of the name reflecting the contents of the
> > 	file, and just number them or something.  (More bikeshedding
> > 	and a different form of confusion.)
> > 
> > 6.	#5, but accompanied by some tool or script that allows easy
> > 	searching of the litmus tests by pattern of interaction.
> > 	(Easy for *me* to say!)
> > 
> > 7.	Something else entirely.
> > 
> > Thoughts?
> 
> Thumbs up for 3.

Very good!  Any nominations for the lucky replacement for "Lock"?

							Thanx, Paul