From: Greg KH <gregkh@linuxfoundation.org>
To: Shivani Agarwal <shivani.agarwal@broadcom.com>,
stable@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com,
linux-kernel@vger.kernel.org, ajay.kaher@broadcom.com,
alexey.makhalov@broadcom.com, tapas.kundu@broadcom.com,
sfrench@samba.org, pc@manguebit.org, ronniesahlberg@gmail.com,
sprasad@microsoft.com, tom@talpey.com, bharathsm@microsoft.com,
linux-cifs@vger.kernel.org, samba-technical@lists.samba.org,
Steve French <stfrench@microsoft.com>,
Cliff Liu <donghua.liu@windriver.com>,
He Zhe <Zhe.He@windriver.com>
Subject: Re: [PATCH v6.1] smb: prevent use-after-free due to open_cached_dir error paths
Date: Fri, 10 Oct 2025 12:52:56 +0200 [thread overview]
Message-ID: <2025101045-unheated-relock-fc67@gregkh> (raw)
In-Reply-To: <aOh20TkmJDG5Bomt@vaarsuvius.home.arpa>
On Thu, Oct 09, 2025 at 08:00:33PM -0700, Paul Aurich wrote:
> Thanks for proposing this! I think this backport has the problem I was
> concerned with when Cliff Liu proposed a backport in March [1].
>
> The handling of the 'has_lease' field in this patch depends on work done by
> two other patches, and those should be backported before this one:
>
> - 5c86919455c1 ("smb: client: fix use-after-free in
> smb2_query_info_compound()")
> - 7afb86733685 ("smb: Don't leak cfid when reconnect races with
> open_cached_dir")
>
> I have (somewhere...) a backport of all three of these patches three patches
> to linux-6.1.y, but it was a while ago and I never found the time to _test_
> the backports.
Now dropped from the queue, thanks for the review.
greg k-h
prev parent reply other threads:[~2025-10-10 10:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 6:08 [PATCH v6.1] smb: prevent use-after-free due to open_cached_dir error paths Shivani Agarwal
2025-10-10 3:00 ` Paul Aurich
2025-10-10 10:52 ` Greg KH [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=2025101045-unheated-relock-fc67@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Zhe.He@windriver.com \
--cc=ajay.kaher@broadcom.com \
--cc=alexey.makhalov@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bharathsm@microsoft.com \
--cc=donghua.liu@windriver.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pc@manguebit.org \
--cc=ronniesahlberg@gmail.com \
--cc=samba-technical@lists.samba.org \
--cc=sfrench@samba.org \
--cc=shivani.agarwal@broadcom.com \
--cc=sprasad@microsoft.com \
--cc=stable@vger.kernel.org \
--cc=stfrench@microsoft.com \
--cc=tapas.kundu@broadcom.com \
--cc=tom@talpey.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;
as well as URLs for NNTP newsgroup(s).