From: Trond Myklebust <trondmy@kernel.org>
To: linux-nfs@vger.kernel.org, Scott Haiden <scott.b.haiden@gmail.com>
Subject: [PATCH 0/4] More server capability fixes
Date: Fri, 29 Aug 2025 12:57:38 -0400 [thread overview]
Message-ID: <cover.1756486626.git.trond.myklebust@hammerspace.com> (raw)
In-Reply-To: <528e7a88-9c63-43d4-8c67-50a36ceda8a7@gmail.com>
From: Trond Myklebust <trond.myklebust@hammerspace.com>
Fix more issues where the client's server capability tracking is
failing.
Trond Myklebust (4):
NFSv4: Don't clear capabilities that won't be reset
NFSv4: Clear the NFS_CAP_FS_LOCATIONS flag if it is not set
NFSv4: Clear NFS_CAP_OPEN_XOR and NFS_CAP_DELEGTIME if not supported
NFSv4: Clear the NFS_CAP_XATTR flag if not supported by the server
fs/nfs/client.c | 2 ++
fs/nfs/nfs4proc.c | 7 ++++---
2 files changed, 6 insertions(+), 3 deletions(-)
--
2.51.0
next prev parent reply other threads:[~2025-08-29 16:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 3:46 [REGRESSION]: NFS 4.2 reports "Operation Not Supported" on getxattr calls Scott Haiden
2025-08-29 3:59 ` Scott Haiden
2025-08-29 16:57 ` Trond Myklebust [this message]
2025-08-29 16:57 ` [PATCH 1/4] NFSv4: Don't clear capabilities that won't be reset Trond Myklebust
2025-08-29 16:57 ` [PATCH 2/4] NFSv4: Clear the NFS_CAP_FS_LOCATIONS flag if it is not set Trond Myklebust
2025-08-29 16:57 ` [PATCH 3/4] NFSv4: Clear NFS_CAP_OPEN_XOR and NFS_CAP_DELEGTIME if not supported Trond Myklebust
2025-08-29 16:57 ` [PATCH 4/4] NFSv4: Clear the NFS_CAP_XATTR flag if not supported by the server Trond Myklebust
2025-08-29 19:21 ` [PATCH 0/4] More server capability fixes Scott Haiden
2025-09-09 3:35 ` Scott Haiden
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.1756486626.git.trond.myklebust@hammerspace.com \
--to=trondmy@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=scott.b.haiden@gmail.com \
/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.