Linux NFS development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: chuck.lever@oracle.com, trond.myklebust@hammerspace.com
Cc: linux-nfs@vger.kernel.org
Subject: [RFC PATCH 0/2] nfsd: simplify and improve nfsd write verifier handling
Date: Tue,  7 Feb 2023 12:41:45 -0500	[thread overview]
Message-ID: <20230207174147.205482-1-jlayton@kernel.org> (raw)

While looking at the recent problems with the fsync during nfsd_file
cleanup, it occured to me that we could greatly simplify and improve
the server's write verifier handling.

Instead of trying to check for errors via fsync and resetting the write
verifier when we get one, we can just fold the current value of the
inode's errseq_t into the hashed verifier that is generated at startup
time.

This is only lightly tested so far. It's a bit difficult to test these
sorts of error handling changes though, since these should be infrequent
events.

Trond, you originally added the code to make it reset the verifier on a
writeback error. Do you have a good way to test that?

Jeff Layton (2):
  errseq: add a new errseq_fetch helper
  nfsd: simplify write verifier handling

 fs/nfsd/filecache.c    | 22 +--------------------
 fs/nfsd/netns.h        |  4 ----
 fs/nfsd/nfs4proc.c     | 17 +++++++---------
 fs/nfsd/nfsctl.c       |  1 -
 fs/nfsd/nfssvc.c       | 44 +++++++++++-------------------------------
 fs/nfsd/trace.h        | 28 ---------------------------
 fs/nfsd/vfs.c          | 28 +++++----------------------
 fs/nfsd/vfs.h          |  1 +
 include/linux/errseq.h |  1 +
 lib/errseq.c           | 33 ++++++++++++++++++++++++++++++-
 10 files changed, 58 insertions(+), 121 deletions(-)

-- 
2.39.1


             reply	other threads:[~2023-02-07 17:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07 17:41 Jeff Layton [this message]
2023-02-07 17:41 ` [RFC PATCH 1/2] errseq: add a new errseq_fetch helper Jeff Layton
2023-02-07 17:41 ` [RFC PATCH 2/2] nfsd: simplify write verifier handling Jeff Layton

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=20230207174147.205482-1-jlayton@kernel.org \
    --to=jlayton@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@hammerspace.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