All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, ncardwell@google.com, kuniyu@google.com,
	netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH net-next] tcp: remove dead code in tcp_rcv_state_process()
Date: Wed, 23 Sep 2026 02:10:12 +0000	[thread overview]
Message-ID: <179012941239.177114.8591343191777304229.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260922010627.2291980-1-edumazet@google.com>

Hello:

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

On Tue, 22 Sep 2026 01:06:27 +0000 you wrote:
> Since commit 3d501dd326fb ("tcp: do not accept ACK of bytes we never
> sent"), tcp_ack() bounds the acceptable old ACK window by
> min(tp->max_window, tp->bytes_acked).
> 
> When sk->sk_state == TCP_SYN_RECV, tp->bytes_acked is always 0, so
> any segment with before(ack, prior_snd_una) immediately returns
> -SKB_DROP_REASON_TCP_TOO_OLD_ACK and never reaches the old_ack label
> (which returns 0).
> 
> [...]

Here is the summary with links:
  - [net-next] tcp: remove dead code in tcp_rcv_state_process()
    https://git.kernel.org/netdev/net-next/c/944ae66642b7

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-09-23  2:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22  1:06 [PATCH net-next] tcp: remove dead code in tcp_rcv_state_process() Eric Dumazet
2026-09-23  1:22 ` Xuanqiang Luo
2026-09-23  2:10 ` 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=179012941239.177114.8591343191777304229.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --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.