All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Altan Hacigumus <ahacigu.linux@gmail.com>
Cc: edumazet@google.com, ncardwell@google.com, kuniyu@google.com,
	davem@davemloft.net, dsahern@kernel.org, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, enchen@paloaltonetworks.com
Subject: Re: [PATCH net v2] tcp: make probe0 timer handle expired user timeout
Date: Tue, 28 Apr 2026 03:00:08 +0000	[thread overview]
Message-ID: <177734520829.218500.17064507281464227634.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260424014639.54110-1-ahacigu.linux@gmail.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 23 Apr 2026 18:46:38 -0700 you wrote:
> tcp_clamp_probe0_to_user_timeout() computes remaining time in jiffies
> using subtraction with an unsigned lvalue.  If elapsed probing time
> exceeds the configured TCP_USER_TIMEOUT, the underflow yields a large
> value.
> 
> This ends up re-arming the probe timer for a full backoff interval
> instead of expiring immediately, delaying connection teardown beyond
> the configured timeout.
> 
> [...]

Here is the summary with links:
  - [net,v2] tcp: make probe0 timer handle expired user timeout
    https://git.kernel.org/netdev/net/c/2b9f6f7065d4

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-04-28  3:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-14  1:36 [PATCH net] tcp: make probe0 timer handle expired user timeout Altan Hacigumus
2026-04-20 18:33 ` Jakub Kicinski
2026-04-20 18:45   ` Eric Dumazet
2026-04-21  4:57 ` Eric Dumazet
2026-04-22  3:31   ` Altan Hacigumus
2026-04-22  7:39     ` Eric Dumazet
2026-04-23  3:02       ` Altan Hacigumus
2026-04-24  1:46 ` [PATCH net v2] " Altan Hacigumus
2026-04-27  7:36   ` Eric Dumazet
2026-04-28  3:00   ` 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=177734520829.218500.17064507281464227634.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ahacigu.linux@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=enchen@paloaltonetworks.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.