From: Trond Myklebust <trondmy@hammerspace.com>
To: Takeshi Nishimura <takeshi.nishimura.linux@gmail.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: Why does Linux nfs not set EXCHGID4_FLAG_SUPP_FENCE_OPS in NFSv4.2 mode?
Date: Thu, 23 Apr 2026 17:32:37 -0400 [thread overview]
Message-ID: <4b02eb62822b3ca363188e48878fbeff636b05fa.camel@hammerspace.com> (raw)
In-Reply-To: <CALWcw=HJ=3FxjLntfFrdjmFa-QKgs29uvna-m8mYRHTeHMJphA@mail.gmail.com>
On Thu, 2026-04-23 at 19:07 +0200, Takeshi Nishimura wrote:
> ?
>
> On Tue, Jan 7, 2025 at 4:41 PM Takeshi Nishimura
> <takeshi.nishimura.linux@gmail.com> wrote:
> >
> > Why does Linux nfs not set EXCHGID4_FLAG_SUPP_FENCE_OPS in NFSv4.2
> > mode?
> >
> > From https://datatracker.ietf.org/doc/html/rfc7862#section-14.1.4
> > A client SHOULD request the EXCHGID4_FLAG_SUPP_FENCE_OPS
> > capability
> > when it sends an EXCHANGE_ID operation. The server SHOULD set
> > this
> > capability in the EXCHANGE_ID reply whether the client requests
> > it or
> > not. It is the server's return that determines whether this
> > capability is in effect. When it is in effect, the following
> > will
> > occur:
> >
> > Why is Linux not doing this?
1. Minor versions are not allowed to introduce a feature and make it
mandatory
2. Why bother, since the server is going to set the flag whether or
not the client requested it?
--
Trond Myklebust Linux NFS client maintainer, Hammerspace
trondmy@kernel.org, trond.myklebust@hammerspace.com
prev parent reply other threads:[~2026-04-23 21:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 15:41 Why does Linux nfs not set EXCHGID4_FLAG_SUPP_FENCE_OPS in NFSv4.2 mode? Takeshi Nishimura
2026-04-23 17:07 ` Takeshi Nishimura
2026-04-23 21:32 ` Trond Myklebust [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=4b02eb62822b3ca363188e48878fbeff636b05fa.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=linux-nfs@vger.kernel.org \
--cc=takeshi.nishimura.linux@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox