From: "Chuck Lever" <cel@kernel.org>
To: "Benji Wiebe" <itsme@benjiwiebe.com>, "Jeff Layton" <jlayton@kernel.org>
Cc: "Linux kernel regressions list" <regressions@lists.linux.dev>,
linux-nfs@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [REGRESSION] reads and writes hang if NFS server has v3 disabled
Date: Fri, 04 Sep 2026 09:09:47 -0400 [thread overview]
Message-ID: <c734eeb8-8486-4491-bb4d-b9656cbaffbe@app.fastmail.com> (raw)
In-Reply-To: <c3d06b9f-7da5-479f-be4f-9c0136631ce9@oracle.com>
[ Adding correct addresses from MAINTAINERS ]
On Fri, Sep 4, 2026, at 9:05 AM, Chuck Lever wrote:
> I'm using a minimal Fedora 45 VM (kvm) for testing. I export a
> directory with rw and mount it from my personal computer running Fedora
> 45 as well. If /etc/nfs. conf has vers3=n, then reads and writes hang in
> D+ state, and there's a continuous
>
>
> I'm using a minimal Fedora 45 VM (kvm) for testing. I export a
> directory with rw and mount it from my personal computer running Fedora
> 45 as well.
> If /etc/nfs.conf has vers3=n, then reads and writes hang in D+ state,
> and there's a continuous loop of V3 NULL calls, with the server replying
> that it only supports v4.
> If nfs.conf has vers3=y, then the reads and writes succeed.
> Introduced in 70b7e3526c53d9dd, still present in the latest
> mainline/master (841e384b841a).
>
> The hung state can be rescued by changing the setting and restarting
> nfs-server, at which point the read/write will complete.
>
> I can do more testing / get more information as needed.
>
> Here's links to pcap files with it working/bugged:
> http://grepper.net/lkml-files/nfs-working.pcap
> http://grepper.net/lkml-files/nfs-bugged.pcap
> http://grepper.net/lkml-files/nfs-bug-kernel.config
>
> #regzbot introduced: 70b7e3526c53d9dd7caccdbeff5b0485640d8cf1
It's not immediately obvious to me why 70b7e3526c53d9dd should
cause this kind of behavior regression.
Jeff, it's a netlink change. Can you triage?
--
Chuck Lever (Come to NFS bake-a-thon! https://nfsv4bat.org)
next parent reply other threads:[~2026-09-04 13:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c26ff09f-48d6-4ef3-9feb-8a8e6d6f37ba@benjiwiebe.com>
[not found] ` <c3d06b9f-7da5-479f-be4f-9c0136631ce9@oracle.com>
2026-09-04 13:09 ` Chuck Lever [this message]
2026-09-04 13:45 ` [REGRESSION] reads and writes hang if NFS server has v3 disabled Jeff Layton
2026-09-04 14:15 ` Chuck Lever
2026-09-04 14:51 ` Jeff Layton
2026-09-07 18:57 ` Benji Wiebe
2026-09-08 9:49 ` Jeff Layton
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=c734eeb8-8486-4491-bb4d-b9656cbaffbe@app.fastmail.com \
--to=cel@kernel.org \
--cc=itsme@benjiwiebe.com \
--cc=jlayton@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