lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 12 Mar 2022 07:40:13 +0000 From: patchwork-bot+netdevbpf@...nel.org To: Jiyong Park <jiyong@...gle.com> Cc: stefanha@...hat.com, sgarzare@...hat.com, mst@...hat.com, jasowang@...hat.com, davem@...emloft.net, kuba@...nel.org, adelva@...gle.com, kvm@...r.kernel.org, virtualization@...ts.linux-foundation.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH net v3 resend] vsock: each transport cycles only on its own sockets Hello: This patch was applied to netdev/net.git (master) by Jakub Kicinski <kuba@...nel.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
Powered by blists - more mailing lists