From: SeongJae Park <sj@kernel.org>
Cc: "Mohamed Abuelfotoh, Hazem" <abuehaze@amazon.com>,
"pc@manguebit.com" <pc@manguebit.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"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>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
"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: Fri, 26 Jan 2024 11:13:51 -0800 [thread overview]
Message-ID: <20240126191351.56183-1-sj@kernel.org> (raw)
In-Reply-To: <53F11617-D406-47C6-8CA7-5BE26EB042BE@amazon.com>
On Mon, 15 Jan 2024 14:22:39 +0000 "Mohamed Abuelfotoh, Hazem" <abuehaze@amazon.com> wrote:
> It looks like both 5.15.146 and 5.10.206 are impacted by this regression as
> they both have the bad commit 33eae65c6f (smb: client: fix OOB in
> SMB2_query_info_init()).
Let me try to tell this to the regression tracking bot, following the doc[1].
This is my first time using #regzbot, so please feel free to correct me if I'm
doing something wrong.
#regzbot introduced: 33eae65c6f
[1] https://docs.kernel.org/admin-guide/reporting-regressions.html#how-do-i-report-a-regression
Thanks,
SJ
[...]
next prev parent reply other threads:[~2024-01-26 19:13 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 [this message]
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
-- 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=20240126191351.56183-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=abuehaze@amazon.com \
--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 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.