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, 4 Mar 2024 08:41:26 -0500	[thread overview]
Message-ID: <ZeXPhjmjHXgK3ANB@manet.1015granger.net> (raw)
In-Reply-To: <ZdyedKSSsIARB4ZC@manet.1015granger.net>

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.
 
Therefore I've started an effort to backport all NFSD commits to
those kernels. The backported commits are destined for the official
LTS kernel branches so that distributions can easily integrate them
into their products.

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

Greg told me this morning that these are now queued for the next
LTS 6.1.y release.


LTS v5.15.y

I have updated this branch to include commits from v6.2.16 through
v5.16, all applied to v5.15.150. The fixes include most NFSD and
fanotify patches in that range. I've begun testing this series, and
so far the backport looks successful.

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


LTS v5.10.y

Backporting is still under way. I've gotten up to v6.0, and plan
to continue to v6.2.16. The fixes include most NFSD and fanotify
patches in that range, but exclude some because v5.10.y does not
include the VFS ID mapping patches that were merged into v5.12.

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


LTS v5.4.y

At this time I am planning not to backport to 5.4.y because of
missing features in this kernel.


-- 
Chuck Lever

  parent reply	other threads:[~2024-03-04 13:41 UTC|newest]

Thread overview: 16+ 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
2024-03-04 13:41 ` Chuck Lever [this message]
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

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=ZeXPhjmjHXgK3ANB@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.