From: Matthieu Baerts <matttbe@kernel.org>
To: Mat Martineau <martineau@kernel.org>
Cc: MPTCP Upstream <mptcp@lists.linux.dev>, Lance Tuller <lance@lance0.com>
Subject: Re: [PATCH mptcp-net] mptcp: fastclose msk when linger time is 0
Date: Wed, 22 Apr 2026 19:07:17 +0200 [thread overview]
Message-ID: <a26748a2-0bdb-4e8b-80d2-c01e44b67059@kernel.org> (raw)
In-Reply-To: <0aebb36a-fabb-d189-255b-d6c630c08c3e@kernel.org>
Hi Mat,
On 22/04/2026 17:35, Mat Martineau wrote:
> On Tue, 21 Apr 2026, Matthieu Baerts (NGI0) wrote:
>
>> The SO_LINGER socket option has been supported for a while with MPTCP
>> sockets [1], but it didn't cause the equivalent of a TCP reset as
>> expected when enabled and its time was set to 0. This was causing some
>> behavioural differences with TCP where some connections were not
>> promptly stopped as expected.
>>
>> To fix that, an extra condition is checked at close() time before
>> sending an MP_FASTCLOSE, the MPTCP equivalent of a TCP reset.
>>
>> Note that backporting up to [1] will be difficult as more changes are
>> needed to be able to send MP_FASTCLOSE. It seems better to stop at [2],
>> which was supposed to already imitate TCP.
>>
>> Validated with MPTCP packetdrill tests [3].
>>
>> Fixes: 268b12387460 ("mptcp: setsockopt: support SO_LINGER") [1]
>> Fixes: d21f83485518 ("mptcp: use fastclose on more edge scenarios") [2]
>> Reported-by: Lance Tuller <lance@lance0.com>
>> Closes: https://github.com/lance0/xfr/pull/67
>> Link: https://github.com/multipath-tcp/packetdrill/pull/196 [3]
>> Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
>> ---
>> net/mptcp/protocol.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> LGTM, thanks Matthieu!
Thank you for the review!
Now in our tree:
New patches for t/upstream-net and t/upstream:
- 0f10cdb3e082: mptcp: fastclose msk when linger time is 0
- Results: 292dd6570cfd..102349628b51 (export-net)
- Results: b3fa12c3ddab..67117a5e3e86 (export)
Tests are now in progress:
- export-net:
https://github.com/multipath-tcp/mptcp_net-next/commit/1acee4b422ad7ee72705775b633d8ae8fa75d508/checks
- export:
https://github.com/multipath-tcp/mptcp_net-next/commit/e676a2d67d616900b5d4be83471f12c5d7a1433e/checks
And the packetdrill PR has been merged.
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2026-04-22 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 15:16 [PATCH mptcp-net] mptcp: fastclose msk when linger time is 0 Matthieu Baerts (NGI0)
2026-04-21 16:52 ` MPTCP CI
2026-04-22 15:35 ` Mat Martineau
2026-04-22 17:07 ` 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=a26748a2-0bdb-4e8b-80d2-c01e44b67059@kernel.org \
--to=matttbe@kernel.org \
--cc=lance@lance0.com \
--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