FAILED: patch "[PATCH] mptcp: pm: ADD_ADDR rtx: allow ID 0" failed to apply to 6.12-stable tree
Subsystems (3)
[email protected]
maintainerThe patch below does not apply to the 6.12-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 <[email protected]>.
To reproduce the conflict and resubmit, you may use the following commands:
git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-6.12.y
git checkout FETCH_HEAD
git cherry-pick -x 03f324f3f1f7619a47b9c91282cb12775ab0a2f1
# <resolve conflicts, build, test, etc.>
git commit -s
git send-email --to '<[email protected]>' --in-reply-to '2026051200-safehouse-jumbo-e3af@gregkh' --subject-prefix 'PATCH 6.12.y' HEAD^..
Possible dependencies:
thanks,
greg k-h
------------------ original commit in Linus's tree ------------------
From 03f324f3f1f7619a47b9c91282cb12775ab0a2f1 Mon Sep 17 00:00:00 2001
From: "Matthieu Baerts (NGI0)" <[email protected]>
Date: Tue, 5 May 2026 17:00:50 +0200
Subject: [PATCH] mptcp: pm: ADD_ADDR rtx: allow ID 0
ADD_ADDR can be sent for the ID 0, which corresponds to the local address and port linked to the initial subflow.
Indeed, this address could be removed, and re-added later on, e.g. what is done in the "delete re-add signal" MPTCP Join selftests. So no reason to ignore it.
net/mptcp/pm.c +0 -3
@@ -337,9 +337,6 @@ static void mptcp_pm_add_timer(struct timer_list *timer)if (inet_sk_state_load (sk) ==TCP_CLOSE )return ; -if (!entry->addr.id) -return ; -if (mptcp_pm_should_add_signal_addr (msk)) {sk_reset_timer (sk, timer, jiffies +TCP_RTO_MAX /8 ); goto out;
Sasha Levin
maintainerPATCH 1/1 mptcp: pm: ADD_ADDR rtx: allow ID 0
From: "Matthieu Baerts (NGI0)" <[email protected]>
[ Upstream commit 03f324f3f1f7619a47b9c91282cb12775ab0a2f1 ]
ADD_ADDR can be sent for the ID 0, which corresponds to the local address and port linked to the initial subflow.
Indeed, this address could be removed, and re-added later on, e.g. what is done in the "delete re-add signal" MPTCP Join selftests. So no reason to ignore it.
--- net/mptcp/pm_netlink.c | 3 --- 1 file changed, 3 deletions(-)
net/mptcp/pm_netlink.c +0 -3
@@ -304,9 +304,6 @@ static void mptcp_pm_add_timer(struct timer_list *timer)if (inet_sk_state_load (sk) ==TCP_CLOSE )return ; -if (!entry->addr.id) -return ; -if (mptcp_pm_should_add_signal_addr (msk)) {sk_reset_timer (sk, timer, jiffies +TCP_RTO_MAX /8 ); goto out;
Signature · 1 line
2.53.0
Matthieu Baerts
maintainerRe: [PATCH 6.12.y] mptcp: pm: ADD_ADDR rtx: allow ID 0
Hi Sasha,
Quoted 11 lines · Sasha Levin
From: "Matthieu Baerts (NGI0)" <[email protected]>
[ Upstream commit
03f324f3f1f7619a47b9c91282cb12775ab0a2f1]
ADD_ADDRcan be sent for the ID 0, which corresponds to the local address and port linked to the initial subflow.Indeed, this address could be removed, and re-added later on, e.g. what is done in the "delete re-add signal" MPTCP Join selftests. So no reason to ignore it.
Quoted 8 lines
Fixes 00cfd77b9063 ("mptcp: retransmit ADD_ADDR when timeout")Reviewed-by Mat Martineau <[email protected]>Signed-off-by Matthieu Baerts (NGI0) <[email protected]>Signed-off-by Jakub Kicinski <[email protected]>[ relocated the 3-line deletion from net/mptcp/pm.c to net/mptcp/pm_netlink.c ]Signed-off-by Sasha Levin <[email protected]>
I just noticed that this patch didn't get applied by Greg. I guess that's similar to other patches: there are conflict after having applied other patches you sent earlier.
I can look at fixing all that.
Cheers,
Matt
Signature · 1 line
Sponsored by the NGI0 Core fund.