From: Matthieu Baerts <matttbe@kernel.org>
To: Sasha Levin <sashal@kernel.org>, stable@vger.kernel.org
Cc: Mat Martineau <martineau@kernel.org>, Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH 6.12.y] mptcp: pm: ADD_ADDR rtx: allow ID 0
Date: Thu, 21 May 2026 09:00:43 +1000 [thread overview]
Message-ID: <b013e8f8-9abe-48d6-ba9c-ad2ee2f8cd91@kernel.org> (raw)
In-Reply-To: <20260518134552.1136532-1-sashal@kernel.org>
Hi Sasha,
On 18/05/2026 23:45, Sasha Levin wrote:
> From: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
>
> [ 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.
>
> Fixes: 00cfd77b9063 ("mptcp: retransmit ADD_ADDR when timeout")
> Cc: stable@vger.kernel.org
> Reviewed-by: Mat Martineau <martineau@kernel.org>
> Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
> Link: https://patch.msgid.link/20260505-net-mptcp-pm-fixes-7-1-rc3-v1-2-fca8091060a4@kernel.org
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> [ relocated the 3-line deletion from net/mptcp/pm.c to net/mptcp/pm_netlink.c ]
> Signed-off-by: Sasha Levin <sashal@kernel.org>
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
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2026-05-20 23:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 14:21 FAILED: patch "[PATCH] mptcp: pm: ADD_ADDR rtx: allow ID 0" failed to apply to 6.12-stable tree gregkh
2026-05-18 13:45 ` [PATCH 6.12.y] mptcp: pm: ADD_ADDR rtx: allow ID 0 Sasha Levin
2026-05-20 23:00 ` Matthieu Baerts [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b013e8f8-9abe-48d6-ba9c-ad2ee2f8cd91@kernel.org \
--to=matttbe@kernel.org \
--cc=kuba@kernel.org \
--cc=martineau@kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox