From: patchwork-bot+netdevbpf@kernel.org
To: Xueming Feng <kuro@kuroa.me>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
lorenzo@google.com, kerneljasonxing@gmail.com, pabeni@redhat.com,
kuba@kernel.org, ncardwell@google.com, ycheng@google.com,
soheil@google.com, dsahern@kernel.org,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH net,v3] tcp: fix forever orphan socket caused by tcp_abort
Date: Tue, 27 Aug 2024 21:30:31 +0000 [thread overview]
Message-ID: <172479423125.767553.13899166301990812537.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240826102327.1461482-1-kuro@kuroa.me>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 26 Aug 2024 18:23:27 +0800 you wrote:
> We have some problem closing zero-window fin-wait-1 tcp sockets in our
> environment. This patch come from the investigation.
>
> Previously tcp_abort only sends out reset and calls tcp_done when the
> socket is not SOCK_DEAD, aka orphan. For orphan socket, it will only
> purging the write queue, but not close the socket and left it to the
> timer.
>
> [...]
Here is the summary with links:
- [net,v3] tcp: fix forever orphan socket caused by tcp_abort
https://git.kernel.org/netdev/net/c/bac76cf89816
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:[~2024-08-27 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 10:23 [PATCH net,v3] tcp: fix forever orphan socket caused by tcp_abort Xueming Feng
2024-08-26 12:11 ` Eric Dumazet
2024-08-27 21:30 ` 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=172479423125.767553.13899166301990812537.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kerneljasonxing@gmail.com \
--cc=kuba@kernel.org \
--cc=kuro@kuroa.me \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=soheil@google.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