From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Siddh Raman Pant <siddh.raman.pant@oracle.com>
Cc: linux-kernel@vger.kernel.org, stable@kernel.org,
Trond Myklebust <trond.myklebust@hammerspace.com>,
Scott Haiden <scott.b.haiden@gmail.com>
Subject: Re: [PATCH 5.15, 5.10, 5.4] NFSv4: Don't clear capabilities that won't be reset
Date: Mon, 29 Sep 2025 15:23:07 +0200 [thread overview]
Message-ID: <2025092953-unsettled-hangup-5721@gregkh> (raw)
In-Reply-To: <20250925125800.74222-1-siddh.raman.pant@oracle.com>
On Thu, Sep 25, 2025 at 06:28:00PM +0530, Siddh Raman Pant wrote:
> From: Trond Myklebust <trond.myklebust@hammerspace.com>
>
> Don't clear the capabilities that are not going to get reset by the call
> to _nfs4_server_capabilities().
>
> Reported-by: Scott Haiden <scott.b.haiden@gmail.com>
> Fixes: b01f21cacde9 ("NFS: Fix the setting of capabilities when automounting a new filesystem")
> Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
> (cherry picked from commit 31f1a960ad1a14def94fa0b8c25d62b4c032813f)
> Signed-off-by: Siddh Raman Pant <siddh.raman.pant@oracle.com>
> ---
> This got backported till 6.1 but not later for some reason. It got
> cherry-picked cleanly.
It's in the queue, just not been released yet, thanks.
greg k-h
prev parent reply other threads:[~2025-09-29 13:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2025091224-CVE-2025-39798-a66e@gregkh>
2025-09-25 12:58 ` Siddh Raman Pant
2025-09-25 13:01 ` [PATCH 5.15 1/3] NFSv4: Clear the NFS_CAP_FS_LOCATIONS flag if it is not set Siddh Raman Pant
2025-09-25 13:01 ` [PATCH 5.15 2/3] NFSv4: Clear NFS_CAP_OPEN_XOR and NFS_CAP_DELEGTIME if not supported Siddh Raman Pant
2025-09-29 13:24 ` Greg Kroah-Hartman
2025-09-29 14:04 ` Siddh Raman Pant
2025-09-25 13:01 ` [PATCH 5.15 3/3] NFSv4: Clear the NFS_CAP_XATTR flag if not supported by the server Siddh Raman Pant
2025-09-25 13:02 ` [PATCH 5.10] " Siddh Raman Pant
2025-09-29 13:23 ` Greg Kroah-Hartman [this message]
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=2025092953-unsettled-hangup-5721@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=scott.b.haiden@gmail.com \
--cc=siddh.raman.pant@oracle.com \
--cc=stable@kernel.org \
--cc=trond.myklebust@hammerspace.com \
/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
all inboxes | Powered by JetHome®