All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: linux-nfs@vger.kernel.org
Cc: trondmy@kernel.org
Subject: [PATCH 00/10] Write verifier fixes and clean-ups
Date: Sun,  2 Jan 2022 12:35:09 -0500	[thread overview]
Message-ID: <164114486506.7344.16096063573748374893.stgit@bazille.1015granger.net> (raw)

Hi-

After a little inebriated holiday consideration, I've come to the
conclusion that returning zero verifiers to STABLE WRITE requests
as reported by Rick Macklem here:

https://lore.kernel.org/linux-nfs/YQXPR0101MB096857EEACF04A6DF1FC6D9BDD749@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM/T/

is a regression because at least one NFS client noticed the
behavior and required a code change to continue interoperating
with the Linux NFS server. The behavior also seems contrary to
spec language in RFC 8881 and RFC 1813.

To address this, I propose the following (during v5.17 merge
window):

1. Roll back
  "nfsd: Add a tracepoint for errors in nfsd4_clone_file_range()"
  "nfsd: Replace use of rwsem with errseq_t"

2. Apply
  "NFSD: Fix verifier returned in stable WRITEs" first so
  that it has a greater opportunity to be back-ported cleanly
  to recent kernels

3. Re-apply patches rolled back in step 1 along with additional
  clean-ups.

Review will show that not all of these new clean-ups are necessary,
but they do eliminate some technical debt that has accrued over the
past few years in this area.

I'm interested in review, comments, or objections.

---

Chuck Lever (8):
      NFSD: Fix verifier returned in stable WRITEs
      NFSD: Clean up nfsd_vfs_write()
      NFSD: De-duplicate net_generic(SVC_NET(rqstp), nfsd_net_id)
      NFSD: De-duplicate net_generic(nf->nf_net, nfsd_net_id)
      NFSD: Write verifier might go backwards
      NFSD: Clean up the nfsd_net::nfssvc_boot field
      NFSD: Rename boot verifier functions
      NFSD: Trace boot verifier resets

Trond Myklebust (2):
      nfsd: Replace use of rwsem with errseq_t
      nfsd: Add a tracepoint for errors in nfsd4_clone_file_range()


 fs/nfsd/filecache.c |   3 +-
 fs/nfsd/filecache.h |   1 -
 fs/nfsd/netns.h     |  11 ++---
 fs/nfsd/nfs4proc.c  |  20 +++++----
 fs/nfsd/nfsctl.c    |   3 +-
 fs/nfsd/nfssvc.c    |  61 ++++++++++++++++++--------
 fs/nfsd/trace.h     |  78 +++++++++++++++++++++++++++++++++
 fs/nfsd/vfs.c       | 104 ++++++++++++++++++++++----------------------
 fs/nfsd/vfs.h       |   3 +-
 9 files changed, 195 insertions(+), 89 deletions(-)

--
Chuck Lever

             reply	other threads:[~2022-01-02 17:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-02 17:35 Chuck Lever [this message]
2022-01-02 17:35 ` [PATCH 01/10] NFSD: Fix verifier returned in stable WRITEs Chuck Lever
2022-01-02 17:35 ` [PATCH 02/10] nfsd: Replace use of rwsem with errseq_t Chuck Lever
2022-01-02 17:35 ` [PATCH 03/10] NFSD: Clean up nfsd_vfs_write() Chuck Lever
2022-01-02 17:35 ` [PATCH 04/10] NFSD: De-duplicate net_generic(SVC_NET(rqstp), nfsd_net_id) Chuck Lever
2022-01-02 17:35 ` [PATCH 05/10] NFSD: De-duplicate net_generic(nf->nf_net, nfsd_net_id) Chuck Lever
2022-01-02 17:35 ` [PATCH 06/10] nfsd: Add a tracepoint for errors in nfsd4_clone_file_range() Chuck Lever
2022-01-02 17:35 ` [PATCH 07/10] NFSD: Write verifier might go backwards Chuck Lever
2022-01-02 17:36 ` [PATCH 08/10] NFSD: Clean up the nfsd_net::nfssvc_boot field Chuck Lever
2022-01-02 17:36 ` [PATCH 09/10] NFSD: Rename boot verifier functions Chuck Lever
2022-01-02 17:36 ` [PATCH 10/10] NFSD: Trace boot verifier resets Chuck Lever

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=164114486506.7344.16096063573748374893.stgit@bazille.1015granger.net \
    --to=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trondmy@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 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.