From: Chuck Lever <chuck.lever@oracle.com>
To: linux-nfs@vger.kernel.org
Subject: long-term stable backports of NFSD patches
Date: Mon, 6 May 2024 09:24:31 -0400 [thread overview]
Message-ID: <ZjjaD4O6FYDrCz8o@tissot.1015granger.net> (raw)
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 kernels between v5.4 and v6.1.
To address the filecache and other scalability problems in those
kernels, I'm preparing backported patches of NFSD fixes for several
popular LTS kernels. These backports are destined for the official
LTS kernel branches so that distributions can easily integrate them
into their products.
Once this effort is complete, Greg and Sasha will continue to be
responsible for backporting NFSD-related fixes from upstream into
the LTS kernels.
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. I'm currently using
the NFS workflows in kdevops as the testing platform, but am
planning to include other tests.
LTS v5.15.y
Work on backporting the NFSD file cache fixes to v5.15.y is now
complete. Subsequent fixes and changes will go through the usual
-> stable@ process.
LTS v5.10.y
I've updated nfsd-5.10.y to include the patches and fixes that
were included in nfsd-5.15.y. You can find these patches in the
"nfsd-5.10.y" branch in the above repo.
This week I intend to set up CI testing for this branch.
--
Chuck Lever
next reply other threads:[~2024-05-06 13:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 13:24 Chuck Lever [this message]
2024-05-08 11:29 ` long-term stable backports of NFSD patches Amir Goldstein
2024-05-08 13:43 ` Chuck Lever
-- strict thread matches above, loose matches on Subject: below --
2024-06-10 13:17 Chuck Lever
2024-06-03 14:04 Chuck Lever
2024-05-28 14:24 Chuck Lever
2024-05-20 14:57 Chuck Lever
2024-05-13 13:31 Chuck Lever III
2024-04-29 13:43 Chuck Lever
2024-04-15 14:06 Chuck Lever
2024-04-09 13:49 Chuck Lever
2024-04-01 14:22 Chuck Lever
2024-03-25 15:26 Chuck Lever III
2024-03-18 13:31 Chuck Lever
2024-03-11 14:08 Chuck Lever
2024-02-26 14:21 Chuck Lever
2024-02-27 5:57 ` Dan Shelton
2024-02-27 14:39 ` Chuck Lever
2024-03-04 13:41 ` 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=ZjjaD4O6FYDrCz8o@tissot.1015granger.net \
--to=chuck.lever@oracle.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).