From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev, edumazet@google.com, ncardwell@google.com,
kuniyu@amazon.com, davem@davemloft.net, dsahern@kernel.org,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
kerneljasonxing@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] tcp: clamp window like before the cleanup
Date: Thu, 06 Mar 2025 23:40:39 +0000 [thread overview]
Message-ID: <174130443900.1819102.16980549477458193974.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250305-net-next-fix-tcp-win-clamp-v1-1-12afb705d34e@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 05 Mar 2025 15:49:48 +0100 you wrote:
> A recent cleanup changed the behaviour of tcp_set_window_clamp(). This
> looks unintentional, and affects MPTCP selftests, e.g. some tests
> re-establishing a connection after a disconnect are now unstable.
>
> Before the cleanup, this operation was done:
>
> new_rcv_ssthresh = min(tp->rcv_wnd, new_window_clamp);
> tp->rcv_ssthresh = max(new_rcv_ssthresh, tp->rcv_ssthresh);
>
> [...]
Here is the summary with links:
- [net-next] tcp: clamp window like before the cleanup
https://git.kernel.org/netdev/net-next/c/8e0e8bef4841
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-03-06 23:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 14:49 [PATCH net-next] tcp: clamp window like before the cleanup Matthieu Baerts (NGI0)
2025-03-06 5:21 ` Jason Xing
2025-03-06 9:45 ` Eric Dumazet
2025-03-06 9:55 ` Matthieu Baerts
2025-03-06 10:02 ` Eric Dumazet
2025-03-06 10:12 ` Matthieu Baerts
2025-03-06 10:16 ` Eric Dumazet
2025-03-06 11:08 ` Eric Dumazet
2025-03-06 11:20 ` Matthieu Baerts
2025-03-06 11:18 ` Jason Xing
2025-03-07 0:31 ` Jason Xing
2025-03-06 23:40 ` patchwork-bot+netdevbpf [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=174130443900.1819102.16980549477458193974.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kerneljasonxing@gmail.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).