From: David Ahern <dsahern@kernel.org>
To: Eric Dumazet <edumazet@google.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Neal Cardwell <ncardwell@google.com>,
Yuchung Cheng <ycheng@google.com>,
netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH net-next 2/4] tcp_metrics: properly set tp->snd_ssthresh in tcp_init_metrics()
Date: Sat, 23 Sep 2023 13:08:57 +0200 [thread overview]
Message-ID: <664f9e63-ec6b-835f-874f-afbae8209b39@kernel.org> (raw)
In-Reply-To: <20230922220356.3739090-3-edumazet@google.com>
On 9/22/23 4:03 PM, Eric Dumazet wrote:
> We need to set tp->snd_ssthresh to TCP_INFINITE_SSTHRESH
> in the case tcp_get_metrics() fails for some reason.
>
> Fixes: 9ad7c049f0f7 ("tcp: RFC2988bis + taking RTT sample from 3WHS for the passive open side")
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> ---
> net/ipv4/tcp_metrics.c | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/net/ipv4/tcp_metrics.c b/net/ipv4/tcp_metrics.c
> index 4bfa2fb27de5481ca3d1300d7e7b2c80d1577a31..0c03f564878ff0a0dbefd9b631f54697346c8fa9 100644
> --- a/net/ipv4/tcp_metrics.c
> +++ b/net/ipv4/tcp_metrics.c
> @@ -470,6 +470,10 @@ void tcp_init_metrics(struct sock *sk)
> u32 val, crtt = 0; /* cached RTT scaled by 8 */
>
> sk_dst_confirm(sk);
> + /* ssthresh may have been reduced unnecessarily during.
> + * 3WHS. Restore it back to its initial default.
> + */
> + tp->snd_ssthresh = TCP_INFINITE_SSTHRESH;
This would read easier with newlines after sk_dst_confirm and again here.
> if (!dst)
> goto reset;
>
> @@ -489,11 +493,6 @@ void tcp_init_metrics(struct sock *sk)
> tp->snd_ssthresh = val;
> if (tp->snd_ssthresh > tp->snd_cwnd_clamp)
> tp->snd_ssthresh = tp->snd_cwnd_clamp;
> - } else {
> - /* ssthresh may have been reduced unnecessarily during.
> - * 3WHS. Restore it back to its initial default.
> - */
> - tp->snd_ssthresh = TCP_INFINITE_SSTHRESH;
> }
> val = tcp_metric_get(tm, TCP_METRIC_REORDERING);
> if (val && tp->reordering != val)
Reviewed-by: David Ahern <dsahern@kernel.org>
next prev parent reply other threads:[~2023-09-23 11:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 22:03 [PATCH net-next 0/4] tcp_metrics: four fixes Eric Dumazet
2023-09-22 22:03 ` [PATCH net-next 1/4] tcp_metrics: add missing barriers on delete Eric Dumazet
2023-09-23 11:09 ` David Ahern
2023-09-24 16:09 ` Neal Cardwell
2023-09-22 22:03 ` [PATCH net-next 2/4] tcp_metrics: properly set tp->snd_ssthresh in tcp_init_metrics() Eric Dumazet
2023-09-23 11:08 ` David Ahern [this message]
2023-09-24 16:09 ` Neal Cardwell
2023-09-22 22:03 ` [PATCH net-next 3/4] tcp_metrics: do not create an entry from tcp_init_metrics() Eric Dumazet
2023-09-23 11:09 ` David Ahern
2023-09-24 16:09 ` Neal Cardwell
2023-09-22 22:03 ` [PATCH net-next 4/4] tcp_metrics: optimize tcp_metrics_flush_all() Eric Dumazet
2023-09-23 11:07 ` David Ahern
2023-10-03 8:04 ` Paolo Abeni
2023-10-03 14:29 ` David Ahern
2023-09-24 16:08 ` Neal Cardwell
2023-10-03 9:40 ` [PATCH net-next 0/4] tcp_metrics: four fixes patchwork-bot+netdevbpf
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=664f9e63-ec6b-835f-874f-afbae8209b39@kernel.org \
--to=dsahern@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ycheng@google.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).