From: Paulo Alcantara <pc@manguebit.com>
To: Michael Krause <mk-debian@galax.is>,
Salvatore Bonaccorso <carnil@debian.org>,
gregkh@linuxfoundation.org, Steve French <stfrench@microsoft.com>,
Michael <mk-debian@galax.is>
Cc: stable@vger.kernel.org, regressions@lists.linux.dev,
linux-cifs@vger.kernel.org
Subject: Re: backporting 24a9799aa8ef ("smb: client: fix UAF in smb2_reconnect_server()") to older stable series
Date: Tue, 03 Dec 2024 10:18:25 -0300 [thread overview]
Message-ID: <1037557ef401a66691a4b1e765eec2e2@manguebit.com> (raw)
In-Reply-To: <2e1ad828-24b3-488d-881e-69232c8c6062@galax.is>
Michael Krause <mk-debian@galax.is> writes:
> On 11/30/24 10:21 AM, Salvatore Bonaccorso wrote:
>> Michael, did a manual backport of 24a9799aa8ef ("smb: client: fix UAF
>> in smb2_reconnect_server()") which seems in fact to solve the issue.
>>
>> Michael, can you please post your backport here for review from Paulo
>> and Steve?
>
> Of course, attached.
>
> Now I really hope I didn't screw it up :)
LGTM. Thanks Michael for the backport.
next prev parent reply other threads:[~2024-12-03 13:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 10:19 FAILED: patch "[PATCH] smb: client: fix UAF in smb2_reconnect_server()" failed to apply to 6.1-stable tree gregkh
2024-11-30 9:21 ` backporting 24a9799aa8ef ("smb: client: fix UAF in smb2_reconnect_server()") to older stable series (was: Re: FAILED: patch "[PATCH] smb: client: fix UAF in smb2_reconnect_server()" failed to apply to 6.1-stable tree) Salvatore Bonaccorso
2024-11-30 11:17 ` backporting 24a9799aa8ef ("smb: client: fix UAF in smb2_reconnect_server()") to older stable series Michael Krause
2024-12-03 13:18 ` Paulo Alcantara [this message]
2024-12-03 14:45 ` Salvatore Bonaccorso
2024-12-09 23:05 ` Michael Krause
2024-12-10 8:51 ` Greg KH
2024-12-10 9:16 ` Salvatore Bonaccorso
2024-12-12 12:26 ` Greg KH
2024-12-12 21:48 ` Michael Krause
2024-12-13 14:33 ` Greg KH
2024-12-13 15:53 ` Salvatore Bonaccorso
2024-12-15 9:25 ` 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=1037557ef401a66691a4b1e765eec2e2@manguebit.com \
--to=pc@manguebit.com \
--cc=carnil@debian.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-cifs@vger.kernel.org \
--cc=mk-debian@galax.is \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=stfrench@microsoft.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