Re: FAILED: patch "[PATCH] selftests: mptcp: join: check RM_ADDR not sent over same" failed to apply to 5.15-stable tree

[Matthieu Baerts <matttbe@kernel.org>]

Hi Greg, Sasha,

On 09/03/2026 11:29, gregkh@linuxfoundation.org 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@vger.kernel.org>.

Thank you for the notification! And thank you Sasha for having resolved
some conflicts already!

(...)

> ------------------ original commit in Linus's tree ------------------
> 
> From 560edd99b5f58b2d4bbe3c8e51e1eed68d887b0e Mon Sep 17 00:00:00 2001
> From: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
> Date: Tue, 3 Mar 2026 11:56:04 +0100
> Subject: [PATCH] selftests: mptcp: join: check RM_ADDR not sent over same
>  subflow
> 
> This validates the previous commit: RM_ADDR were sent over the first
> found active subflow which could be the same as the one being removed.
> It is more likely to loose this notification.
> 
> For this check, RM_ADDR are explicitly dropped when trying to send them
> over the initial subflow, when removing the endpoint attached to it. If
> it is dropped, the test will complain because some RM_ADDR have not been
> received.
> 
> Note that only the RM_ADDR are dropped, to allow the linked subflow to
> be quickly and cleanly closed. To only drop those RM_ADDR, a cBPF byte
> code is used. If the IPTables commands fail, that's OK, the tests will
> continue to pass, but not validate this part. This can be ignored:
> another subtest fully depends on such command, and will be marked as
> skipped.
> 
> 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.

No need to backport this patch: it is just a validation in the selftest
for the parent commit, and the subtest that it modifies is not in v5.15.
CI can use newer selftests version to validate the fix on v5.15.

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