From: patchwork-bot+netdevbpf@kernel.org
To: Jiyong Park <jiyong@google.com>
Cc: stefanha@redhat.com, sgarzare@redhat.com, mst@redhat.com,
jasowang@redhat.com, davem@davemloft.net, kuba@kernel.org,
adelva@google.com, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3 resend] vsock: each transport cycles only on its own sockets
Date: Sat, 12 Mar 2022 07:40:13 +0000 [thread overview]
Message-ID: <164707081324.11016.12108323329246547130.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220311020017.1509316-1-jiyong@google.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 11 Mar 2022 11:00:16 +0900 you wrote:
> When iterating over sockets using vsock_for_each_connected_socket, make
> sure that a transport filters out sockets that don't belong to the
> transport.
>
> There actually was an issue caused by this; in a nested VM
> configuration, destroying the nested VM (which often involves the
> closing of /dev/vhost-vsock if there was h2g connections to the nested
> VM) kills not only the h2g connections, but also all existing g2h
> connections to the (outmost) host which are totally unrelated.
>
> [...]
Here is the summary with links:
- [net,v3,resend] vsock: each transport cycles only on its own sockets
https://git.kernel.org/netdev/net/c/8e6ed963763f
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:[~2022-03-12 7:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 2:00 [PATCH net v3 resend] vsock: each transport cycles only on its own sockets Jiyong Park
2022-03-12 7:40 ` 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=164707081324.11016.12108323329246547130.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=adelva@google.com \
--cc=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=jiyong@google.com \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
/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.