Re: FAILED: patch "[PATCH] selftests: mptcp: join: check re-re-adding ID 0 signal" failed to apply to 5.10-stable tree

[Matthieu Baerts <matttbe@kernel.org>]

Hi Greg,

On 30/08/2024 12:28, gregkh@linuxfoundation.org wrote:
> 
> The patch below does not apply to the 5.10-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@vger.kernel.org>.

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@kernel.org>
> 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")
For the same reasons as the ones invoked for v5.15, no need to backport
this patch to v5.10.

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.