From: Chuck Lever <chuck.lever@oracle.com>
To: Dan Shelton <dan.f.shelton@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: long-term stable backports of NFSD patches
Date: Tue, 27 Feb 2024 09:39:39 -0500 [thread overview]
Message-ID: <Zd30Kwa8s5qlTRdG@manet.1015granger.net> (raw)
In-Reply-To: <CAAvCNcA0KKFF15b9wYTdRcAWTt9udg5K148FoS1MooVANJTKSA@mail.gmail.com>
On Tue, Feb 27, 2024 at 06:57:43AM +0100, Dan Shelton wrote:
> On Mon, 26 Feb 2024 at 15:21, Chuck Lever <chuck.lever@oracle.com> wrote:
> >
> > It's apparent that a number of distributions and their customers
> > remain on long-term stable kernels. We are aware of the scalability
> > problems and other bugs in NFSD in those kernels.
> >
> > Therefore I've started an effort to backport NFSD-related fixes to
> > long-term stable kernels.
> >
> > I consulted with GregKH and Sasha to ask their preferences about how
> > this should be done. They said a full subsystem backport is
> > preferred. Here's a status update.
> >
> > ---
> >
> > I've pushed the NFSD backports to branches in this repo:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git
> >
> > If you are able, I encourage you to pull these, review them or try
> > them out, and report any issues or successes.
> >
> >
> > LTS v6.1.y
>
> Where is LTS v6.6.y?
The purpose of this effort is to address NFSD filecache issues
present until v6.2. v6.6.y, having been released after v6.2,
already has all these fixes, thus there is no need for this effort
to modify it.
Once each of v6.1.y, v5.15.y, and v5.10.y is completed and tested, I
will pass the backported patch series to Greg and Sasha to apply to
the public LTS kernels they maintain.
That will make these backports available to the distributions that
continue to use the public LTS kernels, and enable Greg and Sasha
to continue applying upstream fixes to these kernels automatically.
--
Chuck Lever
next prev parent reply other threads:[~2024-02-27 14:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 14:21 long-term stable backports of NFSD patches Chuck Lever
2024-02-27 5:57 ` Dan Shelton
2024-02-27 14:39 ` Chuck Lever [this message]
2024-03-04 13:41 ` Chuck Lever
-- strict thread matches above, loose matches on Subject: below --
2024-03-11 14:08 Chuck Lever
2024-03-18 13:31 Chuck Lever
2024-03-25 15:26 Chuck Lever III
2024-04-01 14:22 Chuck Lever
2024-04-09 13:49 Chuck Lever
2024-04-15 14:06 Chuck Lever
2024-04-29 13:43 Chuck Lever
2024-05-06 13:24 Chuck Lever
2024-05-08 11:29 ` Amir Goldstein
2024-05-08 13:43 ` Chuck Lever
2024-05-13 13:31 Chuck Lever III
2024-05-20 14:57 Chuck Lever
2024-05-28 14:24 Chuck Lever
2024-06-03 14:04 Chuck Lever
2024-06-10 13:17 Chuck Lever
2024-06-17 14:08 Chuck Lever
2024-06-24 15:39 Chuck Lever
2024-07-01 15:35 Chuck Lever
2024-07-08 15:49 Chuck Lever
2024-07-15 14:30 Chuck Lever
2024-07-22 14:14 Chuck Lever
2024-07-29 15:49 Chuck Lever
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=Zd30Kwa8s5qlTRdG@manet.1015granger.net \
--to=chuck.lever@oracle.com \
--cc=dan.f.shelton@gmail.com \
--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