linux-kernel - Re: Litmus test 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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <494d0375-8f8f-42a3-ae9d-468c3be5aadd@paulmck-laptop>
Date:   Mon, 10 Apr 2023 06:27:15 -0700
From:   "Paul E. McKenney" <paulmck@...nel.org>
To:     David Laight <David.Laight@...lab.com>
Cc:     'Alan Stern' <stern@...land.harvard.edu>,
        Joel Fernandes <joel@...lfernandes.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Boqun Feng <boqun.feng@...il.com>,
        Jade Alglave <j.alglave@....ac.uk>,
        Luc Maranget <luc.maranget@...ia.fr>,
        Peter Zijlstra <peterz@...radead.org>,
        Will Deacon <will.deacon@....com>,
        Jonas Oberhauser <jonas.oberhauser@...weicloud.com>,
        Akira Yokosawa <akiyks@...il.com>,
        Andrea Parri <parri.andrea@...il.com>,
        Daniel Lustig <dlustig@...dia.com>,
        David Howells <dhowells@...hat.com>,
        Jonas Oberhauser <jonas.oberhauser@...wei.com>,
        "linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
        Nicholas Piggin <npiggin@...il.com>,
        Paul Heidekrüger <paul.heidekrueger@...tum.de>,
        Will Deacon <will@...nel.org>
Subject: Re: Litmus test names

On Mon, Apr 10, 2023 at 10:43:52AM +0000, David Laight wrote:
> From: Alan Stern
> > Sent: 06 April 2023 22:36
> > 
> > Paul:
> > 
> > I just saw that two of the files in tools/memory-model/litmus-tests have
> > almost identical names:
> > 
> > 	Z6.0+pooncelock+pooncelock+pombonce.litmus
> > 	Z6.0+pooncelock+poonceLock+pombonce.litmus
> > 
> > They differ only by a lower-case 'l' vs. a capital 'L'.  It's not at all
> > easy to see, and won't play well in case-insensitive filesystems.
> 
> Change the 'L' to a '1' - that'll be ok on case-insensitive
> filesystems :-)

Or just name them all using SHA-1 of the file contents?  ;-)

							Thanx, Paul