From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Sasha Levin <sashal@kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
linux-stable <stable@vger.kernel.org>
Subject: Re: Fwd: [GIT PULL 5.10.y] NFSD filecache fixes
Date: Tue, 18 Jun 2024 14:42:19 +0200 [thread overview]
Message-ID: <2024061849-impure-identical-ea0e@gregkh> (raw)
In-Reply-To: <C268A974-80EA-4F44-A78D-460D881A00C5@oracle.com>
On Mon, Jun 17, 2024 at 07:38:30PM +0000, Chuck Lever III wrote:
> Resend: Corrected email address for stable
>
>
> > Begin forwarded message:
> >
> > From: Chuck Lever <chuck.lever@oracle.com>
> > Subject: [GIT PULL 5.10.y] NFSD filecache fixes
> > Date: June 17, 2024 at 3:30:59 PM EDT
> > To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, Sasha Levin <sashal@kernel.org>
> > Cc: linux-nfs@vger.kernel.org, stable@tissot.1015granger.net
> >
> > Hi Greg, Sasha-
> >
> > Here is a backport of nearly every NFSD patch from v5.11 until
> > v6.3, plus subsequent fixes, onto LTS v5.10.219. This addresses
> > the many NFSD filecache-related scalability problems in v5.10's
> > NFSD. This also contains fixes for issues found in the v5.15
> > NFSD backport over the past several months.
> >
> > I've run this kernel through the usual upstream CI testing for
> > NFSD, and it seems solid.
> >
> > In lieu of sending an mbox containing all of these patches, here's
> > a pull request that gives you the co-ordinates for the full series
> > enabling you to handle the merge however you prefer.
Sasha queued these all up, and I've pushed out a -rc release with _just_
these commits in it, so that it is easier to test and track regressions
for :)
thanks,
greg k-h
next prev parent reply other threads:[~2024-06-18 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 19:30 [GIT PULL 5.10.y] NFSD filecache fixes Chuck Lever
2024-06-17 19:38 ` Fwd: " Chuck Lever III
2024-06-18 12:42 ` Greg Kroah-Hartman [this message]
2024-06-18 13:30 ` 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=2024061849-impure-identical-ea0e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=sashal@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