From: Trond Myklebust <trondmy@kernel.org>
To: Alkis Georgopoulos <alkisg@gmail.com>
Cc: Li Lingfeng <lilingfeng3@huawei.com>, linux-nfs@vger.kernel.org
Subject: [PATCH 0/6] Fix up NFS client mount option regressions
Date: Fri, 28 Nov 2025 23:06:26 -0500 [thread overview]
Message-ID: <cover.1764388528.git.trond.myklebust@hammerspace.com> (raw)
In-Reply-To: <cbd4d74d-21c4-42d6-9442-276fd98313ee@gmail.com>
From: Trond Myklebust <trond.myklebust@hammerspace.com>
The recent changes to suppress the 'ro' and 'rw' mount options when
mounting the same NFS filesystem with different settings are causing
confusion with users, and are an unnecessary restriction. They represent
a functionality regression.
The following patch set reverts the regressions, before applying a
different set of fixes to address the original problem, which was one of
the NFSv4 mount automounter code failing to propagate the correct mount
options.
Trond Myklebust (6):
Revert "nfs: ignore SB_RDONLY when remounting nfs"
Revert "nfs: clear SB_RDONLY before getting superblock"
Revert "nfs: ignore SB_RDONLY when mounting nfs"
NFS: Automounted filesystem should inherit ro,noexec,nodev,sync flags
NFS: Fix inheritance of the block sizes when automounting
NFS: Fix up the automount fs_context to use the correct cred
fs/nfs/client.c | 21 +++++++++++++++++----
fs/nfs/internal.h | 3 +--
fs/nfs/namespace.c | 16 +++++++++++++++-
fs/nfs/nfs4client.c | 18 ++++++++++++++----
fs/nfs/super.c | 33 +++------------------------------
include/linux/nfs_fs_sb.h | 5 +++++
6 files changed, 55 insertions(+), 41 deletions(-)
--
2.52.0
next prev parent reply other threads:[~2025-11-29 4:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 9:39 NFS EACCES regression since 6.15.4 Alkis Georgopoulos
2025-11-29 4:06 ` Trond Myklebust [this message]
2025-11-29 4:06 ` [PATCH 1/6] Revert "nfs: ignore SB_RDONLY when remounting nfs" Trond Myklebust
2025-11-29 4:06 ` [PATCH 2/6] Revert "nfs: clear SB_RDONLY before getting superblock" Trond Myklebust
2025-11-29 4:06 ` [PATCH 3/6] Revert "nfs: ignore SB_RDONLY when mounting nfs" Trond Myklebust
2025-11-29 4:06 ` [PATCH 4/6] NFS: Automounted filesystem should inherit ro,noexec,nodev,sync flags Trond Myklebust
2025-11-29 4:06 ` [PATCH 5/6] NFS: Fix inheritance of the block sizes when automounting Trond Myklebust
2025-11-29 4:06 ` [PATCH 6/6] NFS: Fix up the automount fs_context to use the correct cred Trond Myklebust
2026-01-29 7:06 ` [PATCH 0/6] Fix up NFS client mount option regressions Li Lingfeng
2026-01-29 16:00 ` Trond Myklebust
2026-01-30 1:34 ` Li Lingfeng
2026-01-30 1:43 ` Trond Myklebust
2026-01-30 2:41 ` Li Lingfeng
2026-01-30 3:14 ` Trond Myklebust
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=cover.1764388528.git.trond.myklebust@hammerspace.com \
--to=trondmy@kernel.org \
--cc=alkisg@gmail.com \
--cc=lilingfeng3@huawei.com \
--cc=linux-nfs@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