Linux NFS development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Chuck Lever <cel@kernel.org>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH v2 0/3] NFSD DRC fixes for v6.7-rc
Date: Sat, 11 Nov 2023 07:42:12 -0500	[thread overview]
Message-ID: <3d6a4bacabe0d79eed87f325e73c33df74298404.camel@kernel.org> (raw)
In-Reply-To: <169963305585.5404.9796036538735192053.stgit@bazille.1015granger.net>

On Fri, 2023-11-10 at 11:28 -0500, Chuck Lever wrote:
> I've chased down the reported failures with krb5i/p. Essentially
> the DRC was broken for krb5i/p because of the extra crap those
> security flavors stick before and after the NFS headers.

Huh, so the reported failures were due to retransmissions?

> 
> These patches do address bugs in stable kernels, but they will need
> to be massaged, tested, and applied by hand to get there. Voting now
> open on whether it's worth the trouble for us to do it now, or wait
> until someone complains about a particular LTS problem.
> 
> ---
> 
> Chuck Lever (3):
>       NFSD: Fix "start of NFS reply" pointer passed to nfsd_cache_update()
>       NFSD: Update nfsd_cache_append() to use xdr_stream
>       NFSD: Fix checksum mismatches in the duplicate reply cache
> 
> 
>  fs/nfsd/cache.h    |  4 +--
>  fs/nfsd/nfscache.c | 87 +++++++++++++++++++++++++++-------------------
>  fs/nfsd/nfssvc.c   | 14 ++++++--
>  3 files changed, 65 insertions(+), 40 deletions(-)
> 
> --
> Chuck Lever
> 

Wow, nice work tracking those down. I'm sure that wasn't easy!

Reviewed-by: Jeff Layton <jlayton@kernel.org>

  parent reply	other threads:[~2023-11-11 12:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-10 16:28 [PATCH v2 0/3] NFSD DRC fixes for v6.7-rc Chuck Lever
2023-11-10 16:28 ` [PATCH v2 1/3] NFSD: Fix "start of NFS reply" pointer passed to nfsd_cache_update() Chuck Lever
2023-11-17 14:57   ` Jeff Layton
2023-11-17 15:08     ` Chuck Lever
2023-11-17 18:58       ` Chuck Lever III
2023-11-17 20:11         ` Jeff Layton
2023-11-10 16:28 ` [PATCH v2 2/3] NFSD: Update nfsd_cache_append() to use xdr_stream Chuck Lever
2023-11-10 16:28 ` [PATCH v2 3/3] NFSD: Fix checksum mismatches in the duplicate reply cache Chuck Lever
2023-11-11 12:42 ` Jeff Layton [this message]
2023-11-11 16:09   ` [PATCH v2 0/3] NFSD DRC fixes for v6.7-rc Chuck Lever III

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=3d6a4bacabe0d79eed87f325e73c33df74298404.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=cel@kernel.org \
    --cc=linux-nfs@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox