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: <ZzKpK_9nxh4Qg6mW@tardis.local>
Date: Mon, 11 Nov 2024 17:02:35 -0800
From: Boqun Feng <boqun.feng@...il.com>
To: Sz"oke Benjamin <egyszeregy@...email.hu>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>, paulmck@...nel.org,
	stern@...land.harvard.edu, parri.andrea@...il.com, will@...nel.org,
	peterz@...radead.org, 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
Subject: Re: [PATCH] tools/memory-model: Fix litmus-tests's file names for
 case-insensitive filesystem.

On Tue, Nov 12, 2024 at 12:21:51AM +0100, Sz"oke Benjamin wrote:
> 2024. 11. 11. 23:00 keltezéssel, Linus Torvalds írta:
> > On Mon, 11 Nov 2024 at 13:15, Sz"oke Benjamin <egyszeregy@...email.hu> wrote:
> > > 
> > > There is a technical issue in the Linux kernel source tree's file naming/styles
> > > in git clone command on case-insensitive filesystem.
> > 
> > No.
> > 
> > This is entirely your problem.
> > 
> > The kernel build does not work, and is not intended to work on broken setups.
> > 
> > If you have a case-insensitive filesystem, you get to keep both broken parts.
> > 
> > I actively hate case-insensitive filesystems. It's a broken model in
> > so many ways. I will not lift a finger to try to help that
> > braindamaged setup.
> > 
> > "Here's a nickel, Kid. Go buy yourself a real computer"
> > 
> >               Linus
> 
> 
> In this patch my goal is to improve Linux kernel codebase to able to
> edit/coding in any platform, in an IDE which has a modern GUI.
> 
> Chillout, i am not so stupid to compile kernel on this "braindamaged setup",
> I just like to edit the code and manage it by git commands.
> 

Then you just need to create a case-sensitive partition, no? What's the
*technical* issue of doing that? And that cannot be more challenging
than testing your kernel changes, right? So it won't raise the bar of a
potential serious kernel contributer.

> So, this is a tipical Braindamaged setup in 2024 for Generation of a half of
> Y (like me), Z and Alpha developers.
> 
> Windows or MacOS system
> - Visual Studio Code for coding
>     - Git for manage kernel source
>     - IntelliSense in coding
>     - Live coding with other developers
> 
> Linux remote server
> - Visual Studio Code remote SSH extension/connection for Linux server
>     - Sync kernel workdir with remote Ubuntu/Debian/RHEL Linux server
>     - Remote SSH compile for X86_64, ARM64 etc ...
>     - Download the build result
> 

How do you know it's "typical"? I just googled it and confirmed I'm a
Gen Y ;-) and I'm not using vscode or any IDE, a lot of Gen Y, Z and
Alpha developers I know either use Linux on their desktop/laptop or they
don't use IDEs. May my experience suffice to say it's not typical? Or is
it the case where I thought me and my friends are the whole world? ;-)

> Instead of Visual Studio Code it can be possible to use JetBrains, Eclipse
> and so on any other modern IDE. The actual limitation is only, that there is
> a filename issue in the Linux kernel source with
> "Z6.0+pooncelock+poonceLock+pombonce.litmus", why git clone is failed to
> work well in this case-insensitive OSs.

They are not "case-insensitive" OSes, they support case-sensitive
filesystems, and they support them for a reason, so just use them. With
your changes, it may be OK at clone time, but as soon as you do some
serious development involving `git bisect`, you might be very frustated
that your setup doesn't work.

So your solution is incompleted (not handling the git history), and your
goal is a bit personalized: it's only useful to people who want to
read/edit Linux code without running it and don't want to use a
case-sensitive filesystem, and that's not very persuasive. I don't think
we can accept the solution or commit to that goal.

Regards,
Boqun