Re: FAILED: patch "[PATCH] selftests: mptcp: join: check backup support in signal endp" failed to apply to 5.10-stable tree

[Matthieu Baerts <matttbe@kernel.org>]

Hi Greg,

On 07/08/2024 16:16, 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 f833470c27832136d4416d8fc55d658082af0989 Mon Sep 17 00:00:00 2001
> From: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
> Date: Sat, 27 Jul 2024 12:01:29 +0200
> Subject: [PATCH] selftests: mptcp: join: check backup support in signal endp
> 
> Before the previous commit, 'signal' endpoints with the 'backup' flag
> were ignored when sending the MP_JOIN.
> 
> The MPTCP Join selftest has then been modified to validate this case:
> the "single address, backup" test, is now validating the MP_JOIN with a
> backup flag as it is what we expect it to do with such name. The
> previous version has been kept, but renamed to "single address, switch
> to backup" to avoid confusions.
> 
> The "single address with port, backup" test is also now validating the
> MPJ with a backup flag, which makes more sense than checking the switch
> to backup with an MP_PRIO.
> 
> The "mpc backup both sides" test is now validating that the backup flag
> is also set in MP_JOIN from and to the addresses used in the initial
> subflow, using the special ID 0.
> 
> 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.

FYI, there is no need to backport this patch to v5.10: the modified
tests are not in this version. Some CI will not use these selftests, but
the ones from the last stable version, so no need to worry here.

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