All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: linux-nfs@vger.kernel.org
Subject: long-term stable backports of NFSD patches
Date: Mon, 18 Mar 2024 09:31:56 -0400	[thread overview]
Message-ID: <ZfhCTNJLrrgLTPdM@manet.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. The backported commits 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 v6.1.y

Additional patches were tested and sent to Greg and Sasha this
week. Sasha has merged them into linux-6.1.y for release soon.

Meanwhile, you can find these patches in the "nfsd-6.1.y" branch in
the above repo.


LTS v5.15.y

This branch was rebased on linux-5.15.152 and has completed
testing. I'm investigating some failures in the ltp net.nfs group
but it looks like these are all related to NFSv4.2.

You can find these patches in the "nfsd-5.15.y" branch in the above
repo.


LTS v5.10.y

This branch was rebased on linux-5.10.213. Testing will commence
once nfsd-5.15.y has been sent to Greg and Sasha.

You can find these patches in the "nfsd-5.10.y" branch in the above
repo.

-- 
Chuck Lever

             reply	other threads:[~2024-03-18 13:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-18 13:31 Chuck Lever [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-20 14:57 long-term stable backports of NFSD patches Chuck Lever
2024-05-13 13:31 Chuck Lever III
2024-05-06 13:24 Chuck Lever
2024-05-08 11:29 ` Amir Goldstein
2024-05-08 13:43   ` Chuck Lever
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-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=ZfhCTNJLrrgLTPdM@manet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.