linux-cifs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Salvatore Bonaccorso <carnil@debian.org>
To: Paulo Alcantara <pc@manguebit.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Jan Čermák" <sairon@sairon.cz>,
	"Leonardo Brondani Schenkel" <leonardo@schenkel.net>,
	stable@vger.kernel.org, regressions@lists.linux.dev,
	linux-cifs@vger.kernel.org,
	"Mathias Weißbach" <m.weissbach@info-gate.de>
Subject: Re: [REGRESSION 6.1.70] system calls with CIFS mounts failing with "Resource temporarily unavailable"
Date: Tue, 30 Jan 2024 23:43:52 +0100	[thread overview]
Message-ID: <Zbl7qIcpekgPmLDP@eldamar.lan> (raw)
In-Reply-To: <88a9efbd0718039e6214fd23978250d1@manguebit.com>

Hi Paulo, hi Greg,

Note this is about the 5.10.y backports of the cifs issue, were system
calls fail with "Resource temporarily unavailable".

On Mon, Jan 08, 2024 at 12:58:49PM -0300, Paulo Alcantara wrote:
> Greg Kroah-Hartman <gregkh@linuxfoundation.org> writes:
> 
> > Why can't we just include eb3e28c1e89b ("smb3: Replace smb2pdu 1-element
> > arrays with flex-arrays") to resolve this?
> 
> Yep, this is the right way to go.
> 
> > I've queued it up now.
> 
> Thanks!

Is the underlying issue by picking the three commits:

3080ea5553cc ("stddef: Introduce DECLARE_FLEX_ARRAY() helper")
eb3e28c1e89b ("smb3: Replace smb2pdu 1-element arrays with flex-arrays")

and the last commit in linux-stable-rc for 5.10.y:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit?id=a280ecca48beb40ca6c0fc20dd5a7fdd9b3ee0b7

really fixing the issue?

Since we need to release a new update in Debian, I picked those three
for testing on top of the 5.10.209-1 and while testing explicitly a
cifs mount, I still get:

statfs(".", 0x7ffd809d5a70)             = -1 EAGAIN (Resource temporarily unavailable)

The same happens if I build
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit?id=a280ecca48beb40ca6c0fc20dd5a7fdd9b3ee0b7
(knowing that it is not yet ready for review).

I'm slight confused as a280ecca48be ("cifs: fix off-by-one in
SMB2_query_info_init()") says in the commit message:

[...]
	v5.10.y doesn't have

        eb3e28c1e89b ("smb3: Replace smb2pdu 1-element arrays with flex-arrays")

	and the commit does
[...]

and in meanwhile though the eb3e28c1e89b was picked (in a backported
version). As 6.1.75-rc2 itself does not show the same problem, might
there be a prerequisite missing in the backports for 5.10.y or a
backport being wrong?

Regards,
Salvatore

  reply	other threads:[~2024-01-30 22:43 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8ad7c20e-0645-40f3-96e6-75257b4bd31a@schenkel.net>
2024-01-08 11:18 ` [REGRESSION 6.1.70] system calls with CIFS mounts failing with "Resource temporarily unavailable" 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 [this message]
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
2024-01-15 14:22 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
2024-02-26 22:54         ` Mohamed Abuelfotoh, Hazem

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=Zbl7qIcpekgPmLDP@eldamar.lan \
    --to=carnil@debian.org \
    --cc=gregkh@linuxfoundation.org \
    --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=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 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).