Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB.COM>
To: "'Greg KH'" <gregkh@linuxfoundation.org>,
	"Радослав Ненчовски" <stalliondrift@gmail.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: RE: Kernel 6.6.17-LTS breaks almost all bash scripts involving a directory
Date: Mon, 26 Feb 2024 22:37:10 +0000	[thread overview]
Message-ID: <783a5593b8b248a887bd1d896586dfb3@AcuMS.aculab.com> (raw)
In-Reply-To: <2024022645-zoology-oppose-ea92@gregkh>

From: Greg KH
> Sent: 26 February 2024 16:03
> 
> On Mon, Feb 26, 2024 at 10:52:50AM -0500, Konstantin Ryabitsev wrote:
> > > In the past 4 or 5 years I've been using this script (with an alias) to
> > > compress a single folder:
> > > 7z a "$1.7z" "$1"/ -mx=0 -mmt=8
> > >
> > > I know it doesn't look like much but essentially it creates a 7z archive
> > > (with "store" level of compression) with a name I've entered right after the
> > > alias. For instance: 7z0 "my dir" will create "my dir.7z".
> > > And in the past 4 or 5 years this script was working just fine because it
> > > was recognizing the slash as an indication that the target to compress is a
> > > directory.
> > > However, ever since 6.6.17-LTS arrived (altough I've heard the same
> > > complaints from people who use the regular rolling kernel, but they didn't
> > > tell me which version) bash stopped recognizing the slash as an indication
> > > for directory and thinks of it as the entire root directory, thus it
> > > attempts to compress not only "my dir" but also the whole root (/)
> > > directory. And it doesn't matter whether I'll put the slash between the
> > > quotes or outside of them - the result is the same. And, naturally, it
> > > throws out an unlimited number of errors about "access denied" to everything
> > > in root. I can't even begin to comprehend why on Earth you or whoever writes
> > > the kernel would make this change. Forget about me but ALL linux sysadmins I
> > > know use all kinds of scripts and changing the slash at the end of a word to
> > > mean "root" instead of a sign for directory is a rude way to ruin their
> > > work. Since this change occurred, I can no longer put a directory in an
> > > archive through CLI and I have to do it through GUI, which is about 10 times
> > > slower. I have a DE and I can do that but what about the sysadmins who
> > > usually use linux without a DE or directly SSH into the distro they're
> > > admins of? With this change you're literally hindering their job!
> > >
> > > I downgraded the kernel to 6.6.15-LTS and the problem disappeared - now the
> > > slash is properly recognized as a sign for directory.
> 
> 
> Any chance you can run 'git bisect' to find the offending commit?

And run under strace to see which system call is behaving differently.

	David

> Also, what filesystem type are you seeing this issue on?
> 
> thanks,
> 
> greg k-h

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)


      reply	other threads:[~2024-02-26 22:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa4cd67e-906d-4702-90e2-b9c047320c34@gmail.com>
2024-02-26 15:52 ` Kernel 6.6.17-LTS breaks almost all bash scripts involving a directory Konstantin Ryabitsev
2024-02-26 16:03   ` Greg KH
2024-02-26 22:37     ` David Laight [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=783a5593b8b248a887bd1d896586dfb3@AcuMS.aculab.com \
    --to=david.laight@aculab.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=stable@vger.kernel.org \
    --cc=stalliondrift@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox