From: Greg KH <gregkh@linuxfoundation.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [for v6.12 LTS] nfsd: fix legacy client tracking intialization
Date: Tue, 1 Apr 2025 11:38:40 +0100 [thread overview]
Message-ID: <2025040119-avoid-roast-01ca@gregkh> (raw)
In-Reply-To: <e51834a5-2f11-4783-9065-e19a150283b2@oracle.com>
On Tue, Mar 25, 2025 at 09:21:10AM -0400, Chuck Lever wrote:
> Hi -
>
> Commit de71d4e211ed ("nfsd: fix legacy client tracking initialization")
> should have included a "Cc: stable" tag. Please include it in the next
> release of v6.12 LTS.
>
> BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=219911
>
Also added it to 6.13.y as you don't want someone upgrading and having
bugs.
thanks,
greg k-h
next prev parent reply other threads:[~2025-04-01 10:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 13:21 [for v6.12 LTS] nfsd: fix legacy client tracking intialization Chuck Lever
2025-04-01 10:38 ` Greg KH [this message]
2025-04-01 13:19 ` 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=2025040119-avoid-roast-01ca@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.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