From: Matthieu Baerts <matttbe@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-net 0/4] mptcp: a few fixes
Date: Thu, 13 Aug 2026 13:09:35 +0200 [thread overview]
Message-ID: <9e955f41-a12c-44e1-b3cc-1598a5e59474@kernel.org> (raw)
In-Reply-To: <0858d963-e20e-474a-9f03-ae5d323ff6d1@redhat.com>
Hi Paolo,
On 13/08/2026 08:34, Paolo Abeni wrote:
> On 8/12/26 10:54 PM, Matthieu Baerts wrote:
>> 12 Aug 2026 19:08:30 Paolo Abeni <pabeni@redhat.com>:
>>
>>> This is mostly a follow-up to the recent OoO queue pruning series.
>>> Explicitly targeting net as we have already a lot of patches pending for
>>> net-next, and no need to rush IMHO.
>>
>> (I hope it was OK for me to send a few small cleanup patches)
>
> ATM I haven't checked yet if you already did... but pw says ~400 patches to
> be processed before EoW, I would love if such count is not going to increase:)
Indeed, I understand.
(If I did, can I say it was my cat walking on the keyboard? 😇 Sorry..)
>>> First 2 patches addresses explicit comments from sashiko, 3rd one is a
>>> somewhat unrelated cleanup I stumbled upon while implementing patch 4.
>>>
>>> The last patch fixes another thing implided by sashiko while reviewing
>>> the mentioned series.
>>
>> When reading this, it sounds like there should be 5 patches but only 4
>> have been shared. Just to be sure: is everything there?
> Yes, patch 4 == last patch.
OK, thanks!
> Also patch 4 is the one I think opus 5 could raise some concern on. A safer
> alternative would be replacing it with the following, which is simpler, but I'm
> not fancy of adding another conditional.
Thank you!
> Staging the series a little bit in the export branch will give some time
> to ponder about a better solution.
Fine for me!
> ---
> diff --git a/net/mptcp/protocol.c b/net/mptcp/protocol.c
> index ca644ec53eed..45d627981f15 100644
> --- a/net/mptcp/protocol.c
> +++ b/net/mptcp/protocol.c
> @@ -995,13 +995,15 @@ static bool mptcp_rtx_timer_pending(struct sock *sk)
>
> static void mptcp_reset_rtx_timer(struct sock *sk)
> {
> + struct mptcp_sock *msk = mptcp_sk(sk);
> unsigned long tout;
>
> /* prevent rescheduling on close */
> - if (unlikely(inet_sk_state_load(sk) == TCP_CLOSE))
> + if (unlikely(inet_sk_state_load(sk) == TCP_CLOSE) ||
> + test_bit(MPTCP_FALLBACK_DONE, msk->flags))
> return;
>
> - tout = mptcp_sk(sk)->timer_ival;
> + tout = msk->timer_ival;
> sk_reset_timer(sk, &sk->mptcp_retransmit_timer, jiffies + tout);
> }
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2026-08-13 11:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 17:08 [PATCH mptcp-net 0/4] mptcp: a few fixes Paolo Abeni
2026-08-12 17:08 ` [PATCH mptcp-net 1/4] mptcp: being below memory limit is a likely() condition Paolo Abeni
2026-08-12 17:08 ` [PATCH mptcp-net 2/4] mptcp: avoid pruning for OoW data Paolo Abeni
2026-08-12 17:08 ` [PATCH mptcp-net 3/4] mptcp: remove unneeded READ_ONCE() annotation Paolo Abeni
2026-08-12 17:08 ` [PATCH mptcp-net 4/4] mptcp: do not reschedule the RTX timer for fallback sockets Paolo Abeni
2026-08-12 20:54 ` [PATCH mptcp-net 0/4] mptcp: a few fixes Matthieu Baerts
2026-08-13 6:34 ` Paolo Abeni
2026-08-13 11:09 ` Matthieu Baerts [this message]
2026-08-14 11:38 ` Paolo Abeni
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=9e955f41-a12c-44e1-b3cc-1598a5e59474@kernel.org \
--to=matttbe@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