From: Greg KH <gregkh@linuxfoundation.org>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Chuck Lever <cel@kernel.org>,
linux-stable <stable@vger.kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 0/8] nfsd fixes for 6.5.y
Date: Thu, 30 Nov 2023 13:25:25 +0000 [thread overview]
Message-ID: <2023113013-fanning-esophagus-787f@gregkh> (raw)
In-Reply-To: <3C2A1F40-C0F3-412E-87ED-66AC1A2CA0F4@oracle.com>
On Tue, Nov 28, 2023 at 10:07:11PM +0000, Chuck Lever III wrote:
>
>
> > On Nov 28, 2023, at 4:59 PM, Chuck Lever <cel@kernel.org> wrote:
> >
> > Backport of upstream fixes to NFSD's duplicate reply cache. These
> > have been hand-applied and tested with the same reproducer as was
> > used to create the upstream fixes.
>
> After applying patches 1 through 6 cleanly, these applied with fuzz
> and offset but no rejection -- the same as the 6.6.y patch set.
> The context changes were due to Lorenzo's new nfsd netlink protocol.
6.5.y is now end-of-life, sorry.
greg k-h
next prev parent reply other threads:[~2023-11-30 13:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 21:59 [PATCH 0/8] nfsd fixes for 6.5.y Chuck Lever
2023-11-28 21:59 ` [PATCH 1/8] NFSD: Refactor nfsd_reply_cache_free_locked() Chuck Lever
2023-11-28 22:01 ` kernel test robot
2023-11-28 21:59 ` [PATCH 2/8] NFSD: Rename nfsd_reply_cache_alloc() Chuck Lever
2023-11-28 21:59 ` [PATCH 3/8] NFSD: Replace nfsd_prune_bucket() Chuck Lever
2023-11-28 21:59 ` [PATCH 4/8] NFSD: Refactor the duplicate reply cache shrinker Chuck Lever
2023-11-28 22:00 ` [PATCH 5/8] NFSD: Remove svc_rqst::rq_cacherep Chuck Lever
2023-11-28 22:00 ` [PATCH 6/8] NFSD: Rename struct svc_cacherep Chuck Lever
2023-11-28 22:00 ` [PATCH 7/8] NFSD: Fix "start of NFS reply" pointer passed to nfsd_cache_update() Chuck Lever
2023-11-28 22:00 ` [PATCH 8/8] NFSD: Fix checksum mismatches in the duplicate reply cache Chuck Lever
2023-11-28 22:07 ` [PATCH 0/8] nfsd fixes for 6.5.y Chuck Lever III
2023-11-30 13:25 ` Greg KH [this message]
2023-11-30 13:49 ` 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=2023113013-fanning-esophagus-787f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=stable@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