mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Li Xiasong <lixiasong1@huawei.com>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"mptcp@lists.linux.dev" <mptcp@lists.linux.dev>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-kselftest@vger.kernel.org"
	<linux-kselftest@vger.kernel.org>,
	Eric Dumazet <edumaze@google.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	Mat Martineau <martineau@kernel.org>,
	Geliang Tang <geliang@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Simon Horman <horms@kernel.org>, Shuah Khan <shuah@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	"weiyongjun (A)" <weiyongjun1@huawei.com>,
	yuehaibing <yuehaibing@huawei.com>,
	zhangchangzhong <zhangchangzhong@huawei.com>
Subject: Re: [PATCH net v2 2/6] mptcp: pm: fix ADD_ADDR timer infinite retry on option space insufficient
Date: Mon, 18 May 2026 14:34:43 +0800	[thread overview]
Message-ID: <a462e95c-6aad-4d70-8499-3aa5f090f0a2@huawei.com> (raw)
In-Reply-To: <85b89125-57f2-43ab-a834-4dca56881e26@kernel.org>

Hi, Matt

On 5/17/2026 1:50 PM, Matthieu Baerts wrote:
> Hello,
> 
> On 15/05/2026 06:27, Matthieu Baerts (NGI0) wrote:
>> From: Li Xiasong <lixiasong1@huawei.com>
>>
>> When TCP option space is insufficient (e.g., when sending ADD_ADDR with an
>> IPv6 address and port while tcp_timestamps is enabled), the original code
>> jumped to out_unlock without clearing the addr_signal flag. This caused
>> mptcp_pm_add_timer to keep rescheduling indefinitely, not sending ADD_ADDR,
>> preventing subsequent addresses in the endpoint list from being announced.
> 
> (...)
> 
>> diff --git a/net/mptcp/pm.c b/net/mptcp/pm.c
>> index 3c152bf66cd5..3e770c7407e1 100644
>> --- a/net/mptcp/pm.c
>> +++ b/net/mptcp/pm.c
> 
> (...)
> 
>> @@ -414,8 +420,12 @@ mptcp_pm_del_add_timer(struct mptcp_sock *msk,
>>  	/* Note: entry might have been removed by another thread.
>>  	 * We hold rcu_read_lock() to ensure it is not freed under us.
>>  	 */
>> -	if (stop_timer)
>> -		sk_stop_timer_sync(sk, &entry->add_timer);
> FYI, sashiko found a pre-existing issue here, but I guess that's not
> blocking this series.
> 
> https://sashiko.dev/#/patchset/20260515-net-mptcp-misc-fixes-7-1-rc4-v2-0-701e96419f2f%40kernel.org
> 
> @Li: just to know what I do with this pre-existing issue, do you plan to
> look at it?
> 
> Just in case, I just opened:
> 
>   https://github.com/multipath-tcp/mptcp_net-next/issues/623
> 

Thanks for the heads-up. I’ll take a look at #623 separately and follow up
there.

Best regards,
Li Xiasong

  reply	other threads:[~2026-05-18  6:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-15  4:27 [PATCH net v2 0/6] mptcp: misc fixes for v7.1-rc4 Matthieu Baerts (NGI0)
2026-05-15  4:27 ` [PATCH net v2 1/6] mptcp: do not drop partial packets Matthieu Baerts (NGI0)
2026-05-15  4:27 ` [PATCH net v2 2/6] mptcp: pm: fix ADD_ADDR timer infinite retry on option space insufficient Matthieu Baerts (NGI0)
2026-05-17  5:50   ` Matthieu Baerts
2026-05-18  6:34     ` Li Xiasong [this message]
2026-05-15  4:27 ` [PATCH net v2 3/6] selftests: mptcp: join: cover ADD_ADDR tx drop and list progress Matthieu Baerts (NGI0)
2026-05-15  4:27 ` [PATCH net v2 4/6] mptcp: reset rcv wnd on disconnect Matthieu Baerts (NGI0)
2026-05-15  4:27 ` [PATCH net v2 5/6] mptcp: update window_clamp on subflows when SO_RCVBUF is set Matthieu Baerts (NGI0)
2026-05-15  4:27 ` [PATCH net v2 6/6] selftests: mptcp: drop nanoseconds width specifier Matthieu Baerts (NGI0)
2026-05-17  5:44   ` Matthieu Baerts
2026-05-19 13:50 ` [PATCH net v2 0/6] mptcp: misc fixes for v7.1-rc4 patchwork-bot+netdevbpf

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=a462e95c-6aad-4d70-8499-3aa5f090f0a2@huawei.com \
    --to=lixiasong1@huawei.com \
    --cc=davem@davemloft.net \
    --cc=edumaze@google.com \
    --cc=edumazet@google.com \
    --cc=geliang@kernel.org \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=martineau@kernel.org \
    --cc=matttbe@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shuah@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=weiyongjun1@huawei.com \
    --cc=yuehaibing@huawei.com \
    --cc=zhangchangzhong@huawei.com \
    /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

all inboxes | Powered by JetHome®