From: Chuck Lever <chuck.lever@oracle.com>
To: "stable@vger.kernel.org" <stable@vger.kernel.org>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Rik Theys <rik.theys@gmail.com>
Subject: Two NFSD commits for recent LTS kernels
Date: Tue, 8 Apr 2025 09:35:15 -0400 [thread overview]
Message-ID: <5ea93daf-5419-4396-96fe-91249ece26b6@oracle.com> (raw)
Hi-
These two upstream commits have Fixes: tags, but should have also been
marked "Cc: stable" :
1b3e26a5ccbf ("NFSD: fix decoding in nfs4_xdr_dec_cb_getattr")
4990d098433d ("NFSD: Fix CB_GETATTR status fix")
As far as I can tell, they can be applied to both origin/linux-6.12.y
and origin/linux-6.13.y.
Thanks!
--
Chuck Lever
next reply other threads:[~2025-04-08 13:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 13:35 Chuck Lever [this message]
2025-04-17 14:17 ` Two NFSD commits for recent LTS kernels Greg KH
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=5ea93daf-5419-4396-96fe-91249ece26b6@oracle.com \
--to=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=rik.theys@gmail.com \
--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