All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Petar Sakic <petar.sakic@ink.fish>
Cc: T S Rameshkumar <Rameshkumar.t@phytecembedded.in>,
	MPTCP Linux <mptcp@lists.linux.dev>
Subject: Re: [PATCH v4] mptcp: push queued data on passive TFO subflows becoming established
Date: Thu, 8 Oct 2026 18:10:20 +0200	[thread overview]
Message-ID: <ae2e3936-5467-43ba-a8ce-287202fa50f1@kernel.org> (raw)
In-Reply-To: <CAFPPu1hphgMCQWxUUENR=2+VfE++PG7eW-EeBd1cy8qyPHsDqA@mail.gmail.com>

On 08/10/2026 16:39, Petar Sakic wrote:
>> @Petar: are you working with T S? Because if you suggested the patch, we
>> should at least add a "Suggested-by" tag. Is it OK with the
>> attributions?
> 
> No, I'm not working with T S. I don't know him; he picked up my report
> from the list.
> 
> Suggested-by is fine with me, and so is T S carrying the patch. I'm not
> a kernel developer, so I'm glad someone who can do the formal
> submission and the packetdrill test is taking it on.

Great!

>> (Next time, please send a formal patch to avoid any conflicts here ;))
> 
> Understood, will do.

Note that you can also report issues with MPTCP on GitHub:

  https://github.com/multipath-tcp/mptcp_net-next

> For context: we hit this with xray Shadowsocks-2022 proxies over MPTCP.
> The client puts the whole request in the first write, so small requests
> ride the SYN, and replies from targets close to the server hang. We
> reproduced it in network namespaces at ~120 ms RTT, and the single
> options.c hunk fixed 30/30 requests on 6.12.111. Happy to run our
> reproducer against v6 when it is posted.

Interesting use-case! That's a shame we didn't find this issue earlier.

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


  reply	other threads:[~2026-10-08 16:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08 12:42 [PATCH v4] mptcp: push queued data on passive TFO subflows becoming established T S Rameshkumar
2026-10-08 12:56 ` sashiko-bot
2026-10-08 13:03 ` Matthieu Baerts
     [not found]   ` <PN0PR01MB9382C18780E137E3013A097CF4932@PN0PR01MB9382.INDPRD01.PROD.OUTLOOK.COM>
2026-10-08 13:31     ` Matthieu Baerts
2026-10-08 14:39       ` Petar Sakic
2026-10-08 16:10         ` Matthieu Baerts [this message]
2026-10-12  9:43       ` Matthieu Baerts
2026-10-10  7:40 ` netdev-bot+sashiko
  -- strict thread matches above, loose matches on Subject: below --
2026-10-08 12:16 T S Rameshkumar
2026-10-08 12:29 ` sashiko-bot
2026-10-08 13:42 ` MPTCP CI
     [not found] ` <CADRhS2uk-P8TSmyiM=X5JQXHtzdm68vg6+vyBDr-UCf0EAu0HA@mail.gmail.com>
2026-10-12 13:28   ` Matthieu Baerts
2026-10-12 19:48     ` Petar Sakic
2026-10-13  9:28       ` 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=ae2e3936-5467-43ba-a8ce-287202fa50f1@kernel.org \
    --to=matttbe@kernel.org \
    --cc=Rameshkumar.t@phytecembedded.in \
    --cc=mptcp@lists.linux.dev \
    --cc=petar.sakic@ink.fish \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.