From: patchwork-bot+netdevbpf@kernel.org
To: Longpeng (Mike) <longpeng2@huawei.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
arei.gonglei@huawei.com, davem@davemloft.net, kuba@kernel.org,
jhansen@vmware.com, nslusarek@gmx.net, andraprs@amazon.com,
colin.king@canonical.com, dbrazdil@google.com,
alex.popov@linux.com, sgarzare@redhat.com,
lixianming5@huawei.com
Subject: Re: [PATCH v2] vsock: notify server to shutdown when client has pending signal
Date: Mon, 21 Jun 2021 21:50:04 +0000 [thread overview]
Message-ID: <162431220432.17422.9844505657967304131.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210621062601.1473-1-longpeng2@huawei.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Mon, 21 Jun 2021 14:26:01 +0800 you wrote:
> The client's sk_state will be set to TCP_ESTABLISHED if the server
> replay the client's connect request.
>
> However, if the client has pending signal, its sk_state will be set
> to TCP_CLOSE without notify the server, so the server will hold the
> corrupt connection.
>
> [...]
Here is the summary with links:
- [v2] vsock: notify server to shutdown when client has pending signal
https://git.kernel.org/netdev/net/c/c7ff9cff7060
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:[~2021-06-21 21:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 6:26 [PATCH v2] vsock: notify server to shutdown when client has pending signal Longpeng(Mike)
2021-06-21 10:02 ` Stefano Garzarella
2021-06-21 21:50 ` 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=162431220432.17422.9844505657967304131.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alex.popov@linux.com \
--cc=andraprs@amazon.com \
--cc=arei.gonglei@huawei.com \
--cc=colin.king@canonical.com \
--cc=davem@davemloft.net \
--cc=dbrazdil@google.com \
--cc=jhansen@vmware.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lixianming5@huawei.com \
--cc=longpeng2@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=nslusarek@gmx.net \
--cc=sgarzare@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 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).