From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-nfs <linux-nfs@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: linux-5.15.69 breaks nfs client #forregzbot
Date: Thu, 29 Sep 2022 09:07:33 +0200 [thread overview]
Message-ID: <828c7a9b-66b7-c936-a79a-91d43eaa4a9a@leemhuis.info> (raw)
In-Reply-To: <d9a3460b-0ed6-4bfa-5bdd-032f4bc4ebce@leemhuis.info>
TWIMC: this mail is primarily send for documentation purposes and for
regzbot, my Linux kernel regression tracking bot. These mails usually
contain '#forregzbot' in the subject, to make them easy to spot and filter.
On 23.09.22 09:46, Thorsten Leemhuis wrote:
> Hi, this is your Linux kernel regression tracker. CCing the regression
> mailing list, as it should be in the loop for all regressions, as
> explained here:
> https://www.kernel.org/doc/html/latest/admin-guide/reporting-issues.html
> Also CCing the stable ml, the NFS maintainers, and the authors of
> 31b992b3c39b, too.
>
> On 22.09.22 23:46, Kurt Garloff wrote:
>>
>> a freshly compiled 5.15.69 kernel showed hangs with NFS.
>> Typically mkdir would end up in a 'D' process state, but I
>> have seen ls -l hanging as well.
>> Server is kernel NFS 5.15.69.
>>
>> After reverting the last three NFS related commits,
>> a68a734b19af NFS: Fix WARN_ON due to unionization of nfs_inode.nrequests
>> 3b97deb4abf5 NFS: Fix another fsync() issue after a server reboot
>> 31b992b3c39b NFS: Save some space in the inode
>>
>> things work normally again.
>>
>> As you can see, I suspected 31b992b3c39b ...
>
> FWIW, that's e591b298d7ec in mainline.
>
>> I know this report is light on details; if nothing like this has been
>> reported yet, let me know and I'll try to find some time to investigate
>> further.
>>
>> PS: Please keep me on Cc, I'm not subscribed to linux-nfs.
>
> [...]
>
> #regzbot ^introduced 31b992b3c39b
> #regzbot ignore-activity
#regzbot fixed-by: 27bf7a5d11987
prev parent reply other threads:[~2022-09-29 7:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f6755107-b62c-a388-0ab5-0a6633bf9082@garloff.de>
2022-09-23 7:46 ` linux-5.15.69 breaks nfs client Thorsten Leemhuis
2022-09-29 7:07 ` Thorsten Leemhuis [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=828c7a9b-66b7-c936-a79a-91d43eaa4a9a@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--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).