From: Paolo Abeni <pabeni@redhat.com>
To: Matthieu Baerts <matttbe@kernel.org>, Geliang Tang <geliang@kernel.org>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH v2 mptcp-net 2/2] mptcp: fix duplicate reset on fastclose
Date: Tue, 11 Nov 2025 08:27:21 +0100 [thread overview]
Message-ID: <e2ee6526-a092-4034-8977-1104ccee1fea@redhat.com> (raw)
In-Reply-To: <be209b04-d721-4f75-a05c-56899eb2942f@kernel.org>
On 11/11/25 7:14 AM, Matthieu Baerts wrote:
> 11 Nov 2025 02:59:28 Geliang Tang <geliang@kernel.org>:
>> On Fri, 2025-11-07 at 08:23 +0100, Paolo Abeni wrote:
>>> @@ -2448,7 +2447,7 @@ static void __mptcp_subflow_disconnect(struct
>>> sock *ssk,
>>> unsigned int flags)
>>
>> nit:
>>
>> The 3rd argument "flags" of __mptcp_subflow_disconnect is useless now.
>> We can drop it.
>
> I don't think it is useless: __mptcp_close_ssk() is still called with either
> the push flag or no flag (0).
>
> Because this patch is for net, we should avoid unnecessary modifications:
> we should not change the type or the name of the function argument for
> "cosmetic" reasons.
FWIW, I agree with Mat.
>>> @@ -2511,20 +2510,13 @@ static void __mptcp_close_ssk(struct sock
>>> *sk, struct sock *ssk,
>>> if (dispose_it)
>>> list_del(&subflow->node);
>>>
>>> - if ((flags & MPTCP_CF_FASTCLOSE) &&
>>> !__mptcp_check_fallback(msk)) {
>>> - /* be sure to force the tcp_close path
>>> - * to generate the egress reset
>>> - */
>>> - ssk->sk_lingertime = 0;
>>> - sock_set_flag(ssk, SOCK_LINGER);
>>> - subflow->send_fastclose = 1;
>>> - }
>>> + if (subflow->send_fastclose && ssk->sk_state != TCP_CLOSE)
>>> + tcp_set_state(ssk, TCP_CLOSE);
>>>
>>> need_push = (flags & MPTCP_CF_PUSH) &&
>>> __mptcp_retransmit_pending_data(sk);
>>> if (!dispose_it) {
>>> __mptcp_subflow_disconnect(ssk, subflow, flags);
>>> release_sock(ssk);
>>> -
>
> (This line should not be removed but this can be fixed when applying the patch.)
Thanks!
/P
next prev parent reply other threads:[~2025-11-11 7:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 7:23 [PATCH v2 mptcp-net 0/2] mptcp: fix duplicate reset Paolo Abeni
2025-11-07 7:23 ` [PATCH v2 mptcp-net 1/2] mptcp: decouple mptcp fastclose from tcp close Paolo Abeni
2025-11-11 11:24 ` Matthieu Baerts
2025-11-07 7:23 ` [PATCH v2 mptcp-net 2/2] mptcp: fix duplicate reset on fastclose Paolo Abeni
2025-11-11 1:59 ` Geliang Tang
2025-11-11 6:14 ` Matthieu Baerts
2025-11-11 7:27 ` Paolo Abeni [this message]
2025-11-11 7:49 ` Geliang Tang
2025-11-11 11:24 ` Matthieu Baerts
2025-11-07 8:30 ` [PATCH v2 mptcp-net 0/2] mptcp: fix duplicate reset MPTCP CI
2025-11-11 2:31 ` Geliang Tang
2025-11-11 15:54 ` 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=e2ee6526-a092-4034-8977-1104ccee1fea@redhat.com \
--to=pabeni@redhat.com \
--cc=geliang@kernel.org \
--cc=matttbe@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