All of lore.kernel.org
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "Mohamed Abuelfotoh, Hazem" <abuehaze@amazon.com>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
	SeongJae Park <sj@kernel.org>,
	"pc@manguebit.com" <pc@manguebit.com>,
	"leonardo@schenkel.net" <leonardo@schenkel.net>,
	"linux-cifs@vger.kernel.org" <linux-cifs@vger.kernel.org>,
	"m.weissbach@info-gate.de" <m.weissbach@info-gate.de>,
	"sairon@sairon.cz" <sairon@sairon.cz>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [REGRESSION 6.1.70] system calls with CIFS mounts failing with "Resource temporarily unavailable"
Date: Mon, 26 Feb 2024 15:55:39 +0100	[thread overview]
Message-ID: <2024022604-encrypt-dullness-8127@gregkh> (raw)
In-Reply-To: <fd0174a5-8319-436d-bf05-0f6a3794f6f9@amazon.com>

On Mon, Feb 26, 2024 at 02:28:41PM +0000, Mohamed Abuelfotoh, Hazem wrote:
> On 23/02/2024 06:14, Linux regression tracking #update (Thorsten Leemhuis)
> wrote:
> > CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
> > 
> > 
> 
> > Thx. Took a while (among others because the stable team worked a bit
> > slower that usual), but from what Paulo Alcantara and Salvatore
> > Bonaccorso recently said everything is afaics now fixed or on track to
> > be fixed in all affected stable/longterm branches:
> > https://lore.kernel.org/all/ZdgyEfNsev8WGIl5@eldamar.lan/
> > 
> > If I got this wrong and that's not the case, please holler.
> > 
> > #regzbot resolve: apparently fixed in all affected stable/longterm
> > branches with various commits
> > #regzbot ignore-activity
> > 
> > Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> > --
> > Everything you wanna know about Linux kernel regression tracking:
> > https://linux-regtracking.leemhuis.info/about/#tldr
> > That page also explains what to do if mails like this annoy you.
> > 
> > 
> 
> We are seeing CIFS mount failures after upgrading from v5.15.148 to
> v5.15.149, I have reverted eb3e28c1e8 ("smb3: Replace smb2pdu 1-element
> arrays with flex-arrays") and I no longer see the regression. It looks like
> the issue is also impacting v5.10.y as the mentioned reverted patch has also
> been merged to v5.10.210. I am currently running the CIFS mount test
> manually and will update the thread with the exact mount failure error. I
> think we should revert eb3e28c1e8 ("smb3: Replace smb2pdu 1-element arrays
> with flex-arrays") from both v5.15.y & v5.10.y until we come up with a
> proper fix on this versions, please note that if we will take this path then
> we will need to re-introduce. b3632baa5045 ("cifs: fix off-by-one in
> SMB2_query_info_init()") which has been removed from latest v5.10.y and
> v5.15.y releases.
> 
> 

Please send this as a patch series, in a new thread, so we can properly
track this, we have too many different threads here (and the subject
line is wrong...)

thanks,

greg k-h

  parent reply	other threads:[~2024-02-26 14:55 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15 14:22 [REGRESSION 6.1.70] system calls with CIFS mounts failing with "Resource temporarily unavailable" Mohamed Abuelfotoh, Hazem
2024-01-15 14:28 ` Mohamed Abuelfotoh, Hazem
2024-01-15 15:16   ` gregkh
2024-01-15 15:30     ` Mohamed Abuelfotoh, Hazem
2024-01-31  6:30       ` Salvatore Bonaccorso
2024-01-31 17:19         ` Paulo Alcantara
2024-02-01 12:58           ` Mohamed Abuelfotoh, Hazem
2024-02-03 15:39             ` Salvatore Bonaccorso
2024-02-06  7:46               ` Harshit Mogalapalli
2024-02-06 16:33                 ` kovalev
2024-02-20 20:28                 ` gregkh
2024-02-21  2:26                   ` Harshit Mogalapalli
2024-02-21 11:09                     ` gregkh
2024-01-16 10:23 ` Harshit Mogalapalli
2024-01-26 19:13 ` SeongJae Park
2024-02-23  6:14   ` Linux regression tracking #update (Thorsten Leemhuis)
2024-02-26 14:28     ` Mohamed Abuelfotoh, Hazem
2024-02-26 14:54       ` Linux regression tracking (Thorsten Leemhuis)
2024-02-26 14:55       ` gregkh [this message]
2024-02-26 22:54         ` Mohamed Abuelfotoh, Hazem
  -- strict thread matches above, loose matches on Subject: below --
2024-01-08 10:44 Leonardo Brondani Schenkel
2024-01-08 11:18 ` Jan Čermák
2024-01-08 14:13   ` Greg KH
2024-01-08 14:30     ` Jan Čermák
2024-01-08 14:34     ` Leonardo Brondani Schenkel
2024-01-08 14:52   ` Paulo Alcantara
2024-01-08 15:11     ` Greg Kroah-Hartman
2024-01-08 15:58       ` Paulo Alcantara
2024-01-30 22:43         ` Salvatore Bonaccorso
2024-01-30 22:49           ` Salvatore Bonaccorso
2024-02-20 20:27             ` Greg Kroah-Hartman
2024-02-20 21:25               ` Salvatore Bonaccorso
2024-02-21 11:09                 ` Greg Kroah-Hartman
2024-02-22 23:00                   ` Paulo Alcantara
2024-02-23  5:50                     ` Salvatore Bonaccorso

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=2024022604-encrypt-dullness-8127@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=abuehaze@amazon.com \
    --cc=leonardo@schenkel.net \
    --cc=linux-cifs@vger.kernel.org \
    --cc=m.weissbach@info-gate.de \
    --cc=pc@manguebit.com \
    --cc=regressions@lists.linux.dev \
    --cc=sairon@sairon.cz \
    --cc=sj@kernel.org \
    --cc=stable@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.