[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<168388262147.3920.8279144932756788289.git-patchwork-notify@kernel.org>
Date: Fri, 12 May 2023 09:10:21 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Zhuang Shengen <zhuangshengen@...wei.com>
Cc: sgarzare@...hat.com, virtualization@...ts.linux-foundation.org,
netdev@...r.kernel.org, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org, arei.gonglei@...wei.com, longpeng2@...wei.com,
jianjay.zhou@...wei.com
Subject: Re: [PATCH net v2] vsock: avoid to close connected socket after the
timeout
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@...emloft.net>:
On Thu, 11 May 2023 19:34:30 +0800 you wrote:
> When client and server establish a connection through vsock,
> the client send a request to the server to initiate the connection,
> then start a timer to wait for the server's response. When the server's
> RESPONSE message arrives, the timer also times out and exits. The
> server's RESPONSE message is processed first, and the connection is
> established. However, the client's timer also times out, the original
> processing logic of the client is to directly set the state of this vsock
> to CLOSE and return ETIMEDOUT. It will not notify the server when the port
> is released, causing the server port remain.
> when client's vsock_connect timeout,it should check sk state is
> ESTABLISHED or not. if sk state is ESTABLISHED, it means the connection
> is established, the client should not set the sk state to CLOSE
>
> [...]
Here is the summary with links:
- [net,v2] vsock: avoid to close connected socket after the timeout
https://git.kernel.org/netdev/net/c/6d4486efe9c6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists