Hi Greg,
On 30/08/2024 12:28, gregkh@xxxxxxxxxxxxxxxxxxx wrote:
>
> The patch below does not apply to the 5.15-stable tree.
> If someone wants it applied there, or to any other stable or longterm
> tree, then please email the backport, including the original git commit
> id to <stable@xxxxxxxxxxxxxxx>.
Thank you for the notification!
(...)
> ------------------ original commit in Linus's tree ------------------
>
> From f18fa2abf81099d822d842a107f8c9889c86043c Mon Sep 17 00:00:00 2001
> From: "Matthieu Baerts (NGI0)" <matttbe@xxxxxxxxxx>
> Date: Wed, 28 Aug 2024 08:14:38 +0200
> Subject: [PATCH] selftests: mptcp: join: check re-re-adding ID 0 signal
>
> This test extends "delete re-add signal" to validate the previous
> commit: when the 'signal' endpoint linked to the initial subflow (ID 0)
> is re-added multiple times, it will re-send the ADD_ADDR with id 0. The
> client should still be able to re-create this subflow, even if the
> add_addr_accepted limit has been reached as this special address is not
> considered as a new address.
>
> The 'Fixes' tag here below is the same as the one from the previous
> commit: this patch here is not fixing anything wrong in the selftests,
> but it validates the previous fix for an issue introduced by this commit
> ID.
>
> Fixes: d0876b2284cf ("mptcp: add the incoming RM_ADDR support")
Similar to my previous message mentioning that the 'Fixes' tag here is
pointing at the issue in the code, but the test file cannot easily be
patched to validate the issue: no need to worry about that one for v5.15.
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
