From: bfields@fieldses.org (J. Bruce Fields)
To: Rick Macklem <rmacklem@uoguelph.ca>
Cc: Olga Kornievskaia <olga.kornievskaia@gmail.com>,
"J. Bruce Fields" <bfields@redhat.com>,
Chuck Lever <chuck.lever@oracle.com>,
linux-nfs <linux-nfs@vger.kernel.org>,
nfsv4@ietf.org
Subject: Re: [PATCH 1/1] NFSD fix handling of NFSv4.2 SEEK for data within the last hole
Date: Fri, 2 Apr 2021 17:01:57 -0400 [thread overview]
Message-ID: <20210402210157.GC16427@fieldses.org> (raw)
In-Reply-To: <YQXPR0101MB0968C9AB372DC12408F496D8DD7B9@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM>
Adding nfsv4@ietf.org:
On Thu, Apr 01, 2021 at 09:32:05PM +0000, Rick Macklem wrote:
> I discussed this on nfsv4@ietf.org some time ago.
> The problem with "fixing" the server is that it breaks
> the unpatched Linux client.
>
> If the client is careful, it can work correctly for both a Linux
> and RFC5661 conformant server. That's what the FreeBSD
> client tries to do.
> --> I'd suggest that be your main goal.
>
> The FreeBSD server ships "Linux compatible", but there is
> a switch to make it RFC5661 compatible.
> --> I wouldn't make it default the RFC compatible for
> quite a while after the client that handles RFC compatible
> ships.
>
> I tried to convince folks to "errata" the RFC to Linux
> compatible (since Linux was the only shipping 4.2 at
> the time, but they did not consider it an "errata").
Previous discussion here:
https://mailarchive.ietf.org/arch/msg/nfsv4/bPLFnywt1wZ4kolMkzeSYca0qIM/
There's no rejection on that thread, was it elsewhere?
--b.
next prev parent reply other threads:[~2021-04-02 21:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 19:28 [PATCH 1/1] NFSD fix handling of NFSv4.2 SEEK for data within the last hole Olga Kornievskaia
2021-04-01 1:50 ` J. Bruce Fields
2021-04-01 13:27 ` Olga Kornievskaia
2021-04-01 21:32 ` Rick Macklem
2021-04-02 21:01 ` J. Bruce Fields [this message]
[not found] ` <CADaq8jeNrA3TexAM0dBxj7LSoooyRna6wU-VomDKovodYTdqKA@mail.gmail.com>
2021-04-05 14:06 ` [nfsv4] " J. Bruce Fields
2021-04-09 20:24 ` Frank Filz
2021-04-02 14:32 ` J. Bruce Fields
2021-04-09 18:39 ` Olga Kornievskaia
2021-04-11 16:43 ` Chuck Lever III
2021-04-13 15:01 ` J. Bruce Fields
2021-04-13 15:31 ` Olga Kornievskaia
2021-04-13 17:30 ` J. Bruce Fields
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=20210402210157.GC16427@fieldses.org \
--to=bfields@fieldses.org \
--cc=bfields@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=nfsv4@ietf.org \
--cc=olga.kornievskaia@gmail.com \
--cc=rmacklem@uoguelph.ca \
/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.