From: Greg KH <gregkh@linuxfoundation.org>
To: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev, stable@vger.kernel.org,
Mat Martineau <martineau@kernel.org>,
Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH 6.1.y 1/2] mptcp: pm: reuse ID 0 after delete and re-add
Date: Wed, 4 Sep 2024 16:31:53 +0200 [thread overview]
Message-ID: <2024090450-engross-unpeeled-a74d@gregkh> (raw)
In-Reply-To: <20240904110306.4082410-5-matttbe@kernel.org>
On Wed, Sep 04, 2024 at 01:03:08PM +0200, Matthieu Baerts (NGI0) wrote:
> commit 8b8ed1b429f8fa7ebd5632555e7b047bc0620075 upstream.
>
Applied
next prev parent reply other threads:[~2024-09-04 14:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 12:07 FAILED: patch "[PATCH] mptcp: pm: avoid possible UaF when selecting endp" failed to apply to 6.1-stable tree gregkh
2024-09-04 10:57 ` [PATCH 6.1.y] mptcp: pm: avoid possible UaF when selecting endp Matthieu Baerts (NGI0)
2024-09-04 11:03 ` [PATCH 6.1.y 0/2] Backport of "mptcp: pm: reuse ID 0 after delete and re-add" and more Matthieu Baerts (NGI0)
2024-09-04 11:03 ` [PATCH 6.1.y 1/2] mptcp: pm: reuse ID 0 after delete and re-add Matthieu Baerts (NGI0)
2024-09-04 14:31 ` Greg KH [this message]
2024-09-04 14:32 ` Patch "mptcp: pm: reuse ID 0 after delete and re-add" has been added to the 6.1-stable tree gregkh
2024-09-04 11:03 ` [PATCH 6.1.y 2/2] mptcp: pm: fix ID 0 endp usage after multiple re-creations Matthieu Baerts (NGI0)
2024-09-04 14:31 ` Greg KH
2024-09-04 14:32 ` Patch "mptcp: pm: fix ID 0 endp usage after multiple re-creations" has been added to the 6.1-stable tree gregkh
2024-09-04 14:31 ` [PATCH 6.1.y] mptcp: pm: avoid possible UaF when selecting endp Greg KH
2024-09-04 14:32 ` Patch "mptcp: pm: avoid possible UaF when selecting endp" has been added to the 6.1-stable tree gregkh
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=2024090450-engross-unpeeled-a74d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.