MPTCP Linux Development
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: mptcp@lists.linux.dev
Cc: geliang@kernel.org, Mat Martineau <martineau@kernel.org>
Subject: [PATCH v2 mptcp-net 0/2] mptcp: restore zero window probe
Date: Wed, 22 Oct 2025 09:39:57 +0200	[thread overview]
Message-ID: <cover.1761118636.git.pabeni@redhat.com> (raw)

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?

[1] at least here, at least with the packet drill reproducer ;)
---
v1 -> v2:
  - drop unneeded delta in patch 1/2

Paolo Abeni (2):
  mptcp: restore window probe
  mptcp: zero window probe mib

 net/mptcp/mib.c      | 1 +
 net/mptcp/mib.h      | 1 +
 net/mptcp/protocol.c | 8 +++++++-
 3 files changed, 9 insertions(+), 1 deletion(-)

-- 
2.51.0


             reply	other threads:[~2025-10-22  7:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-22  7:39 Paolo Abeni [this message]
2025-10-22  7:39 ` [PATCH v2 mptcp-net 1/2] mptcp: restore window probe 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
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=cover.1761118636.git.pabeni@redhat.com \
    --to=pabeni@redhat.com \
    --cc=geliang@kernel.org \
    --cc=martineau@kernel.org \
    --cc=mptcp@lists.linux.dev \
    /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