MPTCP Linux Development
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>,
	Paolo Abeni <pabeni@redhat.com>,
	mptcp@lists.linux.dev
Cc: Mat Martineau <martineau@kernel.org>
Subject: Re: [PATCH v2 mptcp-net 0/2] mptcp: restore zero window probe
Date: Thu, 23 Oct 2025 17:54:18 +0200	[thread overview]
Message-ID: <2dc7ad69-e264-4733-a953-8368ee2a0b44@kernel.org> (raw)
In-Reply-To: <f7e3bb32be02262fa77a5311640f2282e4acdfbc.camel@kernel.org>

Hi Geliang,

On 23/10/2025 08:24, Geliang Tang wrote:
> Hi Paolo,
> 
> On Wed, 2025-10-22 at 18:07 +0800, Geliang Tang wrote:
>> Hi Paolo,
>>
>> On Wed, 2025-10-22 at 09:39 +0200, Paolo Abeni wrote:
>>> It turns out that the issue reported by Geliang on the pending
>>> backlog
>>> patches is actually on older one that the new code made more easy
>>> reproducible.
>>>
>>> The first patch in the series addresses it[1], the 2nd one
>>> introduce
>>> new
>>> mibs to hopefully catch this problem sooned.
>>>
>>> I have a pktdrill to validate this scenario. I'll share that soon.
>>>
>>> @Geliang could you please validate the above in your testbed, on
>>> top
>>> of
>>> the backlog and splice patches?
>>
>> Thanks very much. I've already started testing, and so far everything
>> is running smoothly. I'll let it run loop tests overnight and will
>> have
>> the results by tomorrow morning. I'll provide you with feedback then.
> 
> Thank you so much! This fix really works. I've run hundreds of splice
> test loops with the following three patchsets applied, and no test
> failures occurred:
> 
> 	mptcp: restore zero window probe, v2
> 	mptcp: introduce backlog processing, v6
> 	implement mptcp read_sock, v13
> 
> Please add my tag for this set:
> 
> 	Reported-and-tested-by: Geliang Tang <geliang@kernel.org>

Thank you for the test!

To avoid issues with checkpatch and to be consistent, I'm going to add
this on the first patch:

  Reported-by: (...)
  Closes:
https://lore.kernel.org/d0a814c364e744ca6b836ccd5b6e9146882e8d42.camel@kernel.org
  (...)
  Tested-by: (...)

And only the Tested-by on the second one. I hope that's OK!

>> Thanks,
>> -Geliang
>>
>>>
>>> [1] at least here, at least with the packet drill reproducer ;)
>>> ---
>>> v1 -> v2:
>>>   - drop unneeded delta in patch 1/2
> 
> This change in v1 is valid. Later I will send a dedicated cleanup patch
> for -next to use tcp_sk() in mptcp_sendmsg_frag() with your "Suggested-
> by" tag.

Please only add such patch when we modify code around in net-next.

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


  reply	other threads:[~2025-10-23 15:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-22  7:39 [PATCH v2 mptcp-net 0/2] mptcp: restore zero window probe Paolo Abeni
2025-10-22  7:39 ` [PATCH v2 mptcp-net 1/2] mptcp: restore " Paolo Abeni
2025-10-22  7:39 ` [PATCH v2 mptcp-net 2/2] mptcp: zero window probe mib Paolo Abeni
2025-10-23 16:26   ` Matthieu Baerts
2025-10-24  7:30     ` Paolo Abeni
2025-10-24  8:07       ` Matthieu Baerts
2025-10-22  8:55 ` [PATCH v2 mptcp-net 0/2] mptcp: restore zero window probe MPTCP CI
2025-10-22 10:07 ` Geliang Tang
2025-10-23  6:24   ` Geliang Tang
2025-10-23 15:54     ` Matthieu Baerts [this message]
2025-10-24  9:03       ` Geliang Tang
2025-10-23 16:23 ` Matthieu Baerts

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=2dc7ad69-e264-4733-a953-8368ee2a0b44@kernel.org \
    --to=matttbe@kernel.org \
    --cc=geliang@kernel.org \
    --cc=martineau@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=pabeni@redhat.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