From: Salvatore Bonaccorso <carnil@debian.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Paulo Alcantara <pc@manguebit.com>,
regressions@lists.linux.dev,
Steve French <stfrench@microsoft.com>,
sashal@kernel.org, stable@vger.kernel.org,
linux-cifs@vger.kernel.org
Subject: Re: [regression 6.1.80+] "CIFS: VFS: directory entry name would overflow frame end of buf" and invisible files under certain conditions and at least with noserverino mount option
Date: Mon, 29 Apr 2024 17:11:47 +0200 [thread overview]
Message-ID: <Zi-4s-7QSFO1OR17@eldamar.lan> (raw)
In-Reply-To: <2024042912-unloader-slighting-c756@gregkh>
Hi,
On Mon, Apr 29, 2024 at 12:50:45PM +0200, Greg KH wrote:
> On Tue, Apr 23, 2024 at 10:58:09PM +0200, Salvatore Bonaccorso wrote:
> > Hi Paulo,
> >
> > On Mon, Apr 22, 2024 at 12:08:53PM -0300, Paulo Alcantara wrote:
> > > Salvatore Bonaccorso <carnil@debian.org> writes:
> > >
> > > > I'm still failing to provide you a recipe with a minimal as possible
> > > > setup, but with the instance I was able to reproduce the issue the
> > > > regression seems gone with cherry-picking 35235e19b393 ("cifs: Replace
> > > > remaining 1-element arrays") .
> > >
> > > It's OK, no problem. Could you please provide the backport to stable
> > > team?
> >
> > Sure, here it is. Greg or Sasha is it ok to pick that up for the 6.1.y
> > queues?
>
> Glad to, for some reason I thought this caused problems, but if it
> passes your testing, great! I'll go queue it up now, thanks.
Thanks! Unfortunately I'm not having a good test(case/suite) for this
myself for such cases. All issues recently forwarded as regressions in
the 6.1.y series were unfortunately only uncovered by Debian users
once we did release the version :(. Hopefully this will "calm down"
now.
Thanks to all of you, for your work!
Regards,
Salvatore
prev parent reply other threads:[~2024-04-29 15:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 21:44 [regression 6.1.80+] "CIFS: VFS: directory entry name would overflow frame end of buf" and invisible files under certain conditions and at least with noserverino mount option Salvatore Bonaccorso
2024-04-17 22:58 ` Paulo Alcantara
2024-04-18 4:58 ` Salvatore Bonaccorso
2024-04-18 13:47 ` Paulo Alcantara
2024-04-19 20:12 ` Salvatore Bonaccorso
2024-04-22 15:08 ` Paulo Alcantara
2024-04-23 20:58 ` Salvatore Bonaccorso
2024-04-29 10:50 ` Greg KH
2024-04-29 15:11 ` Salvatore Bonaccorso [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=Zi-4s-7QSFO1OR17@eldamar.lan \
--to=carnil@debian.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-cifs@vger.kernel.org \
--cc=pc@manguebit.com \
--cc=regressions@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=stfrench@microsoft.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;
as well as URLs for NNTP newsgroup(s).