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/2] nfsd fixes for 6.6.y
Date: Thu, 30 Nov 2023 13:28:45 +0000 [thread overview]
Message-ID: <2023113035-monologue-stump-645c@gregkh> (raw)
In-Reply-To: <E01AE605-9548-40AF-A72D-01D46B8A749E@oracle.com>
On Tue, Nov 28, 2023 at 10:05:45PM +0000, Chuck Lever III wrote:
>
>
> > On Nov 28, 2023, at 4:58 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.
>
> These applied with fuzz and offset but no rejection.
All now queued up, thanks.
greg k-h
prev parent reply other threads:[~2023-11-30 13:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 21:58 [PATCH 0/2] nfsd fixes for 6.6.y Chuck Lever
2023-11-28 21:58 ` [PATCH 1/2] NFSD: Fix "start of NFS reply" pointer passed to nfsd_cache_update() Chuck Lever
2023-11-28 21:59 ` kernel test robot
2023-11-28 21:58 ` [PATCH 2/2] NFSD: Fix checksum mismatches in the duplicate reply cache Chuck Lever
2023-11-28 22:05 ` [PATCH 0/2] nfsd fixes for 6.6.y Chuck Lever III
2023-11-30 13:28 ` Greg KH [this message]
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=2023113035-monologue-stump-645c@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