vsock: forward all packets to the host when no H2G is registered
Subsystems (3)
Stefano Garzarella
maintainerPATCH 1/1 vsock: forward all packets to the host when no H2G is registered
Before commit c0cfa2d8a788 ("vsock: add multi-transports support"), if a G2H transport was loaded (e.g. virtio transport), every packets was forwarded to the host, regardless of the destination CID. The H2G transports implemented until then (vhost-vsock, VMCI) always responded with an error, if the destination CID was not VMADDR_CID_HOST.
From that commit, we are using the remote CID to decide which transport to use, so packets with remote CID > VMADDR_CID_HOST(2) are sent only through H2G transport. If no H2G is available, packets are discarded directly in the guest.
Some use cases (e.g. Nitro Enclaves [1]) rely on the old behaviour to implement sibling VMs communication, so we restore the old behavior when no H2G is registered.
It will be up to the host to discard packets if the destination is not the right one. As it was already implemented before adding multi-transport support.
Tested with nested QEMU/KVM by me and Nitro Enclaves by Andra.
[1] Documentation/virt/ne_overview.rst
--- net/vmw_vsock/af_vsock.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/vmw_vsock/af_vsock.c +1 -1
@@ -438,7 +438,7 @@ int vsock_assign_transport(struct vsock_sock *vsk, struct vsock_sock *psk)case SOCK_STREAM :if (vsock_use_local_transport (remote_cid)) new_transport = transport_local; -else if (remote_cid <=VMADDR_CID_HOST ) +else if (remote_cid <=VMADDR_CID_HOST || !transport_h2g) new_transport = transport_g2h;else new_transport = transport_h2g;
Signature · 1 line
2.26.2
This patch was applied to netdev/net.git (refs/heads/master):
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
Quoted 8 lines · On Thu, 12 Nov 2020 14:38:37 +0100 you wrote:
Before commit
c0cfa2d8a788("vsock: add multi-transports support"), if a G2H transport was loaded (e.g. virtio transport), every packets was forwarded to the host, regardless of the destination CID. The H2G transports implemented until then (vhost-vsock, VMCI) always responded with an error, if the destination CID was notVMADDR_CID_HOST.[...]
Here is the summary with links:
- [net] vsock: forward all packets to the host when no H2G is registered
https://git.kernel.org/netdev/net/c/65b422d9b61b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Quoted 29 lines · Stefano Garzarella
Before commit
c0cfa2d8a788("vsock: add multi-transports support"), if a G2H transport was loaded (e.g. virtio transport), every packets was forwarded to the host, regardless of the destination CID. The H2G transports implemented until then (vhost-vsock, VMCI) always responded with an error, if the destination CID was notVMADDR_CID_HOST.From that commit, we are using the remote CID to decide which transport to use, so packets with remote CID >
VMADDR_CID_HOST(2)are sent only through H2G transport. If no H2G is available, packets are discarded directly in the guest.Some use cases (e.g. Nitro Enclaves [1]) rely on the old behaviour to implement sibling VMs communication, so we restore the old behavior when no H2G is registered.
It will be up to the host to discard packets if the destination is not the right one. As it was already implemented before adding multi-transport support.Tested with nested QEMU/KVM by me and Nitro Enclaves by Andra.
[1]
Documentation/virt/ne_overview.rstCc Jorgen Hansen <[email protected]>Cc Dexuan Cui <[email protected]>Fixes c0cfa2d8a788 ("vsock: add multi-transports support")Reported-by Andra Paraschiv <[email protected]>Tested-by Andra Paraschiv <[email protected]>Signed-off-by Stefano Garzarella <[email protected]>
Quoted 3 lines
--- net/vmw_vsock/af_vsock.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Quoted 33 lines · Stefan Hajnoczi
Quoted 29 lines · Stefano Garzarella
Before commit
c0cfa2d8a788("vsock: add multi-transports support"), if a G2H transport was loaded (e.g. virtio transport), every packets was forwarded to the host, regardless of the destination CID. The H2G transports implemented until then (vhost-vsock, VMCI) always responded with an error, if the destination CID was notVMADDR_CID_HOST.From that commit, we are using the remote CID to decide which
transport to use, so packets with remote CID >VMADDR_CID_HOST(2)are sent only through H2G transport. If no H2G is available, packets are discarded directly in the guest.Some use cases (e.g. Nitro Enclaves [1]) rely on the old behaviour to implement sibling VMs communication, so we restore the old behavior when no H2G is registered.
It will be up to the host to discard packets if the destination is not the right one. As it was already implemented before adding multi-transport support.Tested with nested QEMU/KVM by me and Nitro Enclaves by Andra.
[1]
Documentation/virt/ne_overview.rstCc Jorgen Hansen <[email protected]>Cc Dexuan Cui <[email protected]>Fixes c0cfa2d8a788 ("vsock: add multi-transports support")Reported-by Andra Paraschiv <[email protected]>Tested-by Andra Paraschiv <[email protected]>Signed-off-by Stefano Garzarella <[email protected]>Quoted 3 lines
--- net/vmw_vsock/af_vsock.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Quoted 1 line
Acked-by Stefan Hajnoczi <[email protected]>
Is there anything we have to do to also get this into the affected stable trees? :)
Alex
Amazon Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss Eingetragen am Amtsgericht Charlottenburg unter HRB 149173 B
Sitz: Berlin
Ust-ID: DE 289 237 879
Stefano Garzarella
maintainerQuoted 35 lines · Alexander Graf
Quoted 33 lines · Stefan Hajnoczi
Quoted 32 lines · Stefano Garzarella
Before commit
c0cfa2d8a788("vsock: add multi-transports support"), if a G2H transport was loaded (e.g. virtio transport), every packets was forwarded to the host, regardless of the destination CID. The H2G transports implemented until then (vhost-vsock, VMCI) always responded with an error, if the destination CID was notVMADDR_CID_HOST.From that commit, we are using the remote CID to decide which transport to use, so packets with remote CID >
VMADDR_CID_HOST(2)are sent only through H2G transport. If no H2G is available, packets are discarded directly in the guest.Some use cases (e.g. Nitro Enclaves [1]) rely on the old behaviour to implement sibling VMs communication, so we restore the old behavior when no H2G is registered.
It will be up to the host to discard packets if the destination is not the right one. As it was already implemented before adding multi-transport support.Tested with nested QEMU/KVM by me and Nitro Enclaves by Andra.
[1]
Documentation/virt/ne_overview.rstCc Jorgen Hansen <[email protected]>Cc Dexuan Cui <[email protected]>Fixes c0cfa2d8a788 ("vsock: add multi-transports support")Reported-by Andra Paraschiv <[email protected]>Tested-by Andra Paraschiv <[email protected]>Signed-off-by Stefano Garzarella <[email protected]>--- net/vmw_vsock/af_vsock.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Quoted 5 lines
Quoted 1 line
Acked-by Stefan Hajnoczi <[email protected]>Is there anything we have to do to also get this into the affected stable trees? :)
The patch is already queued by Jakub in the netdev stable queue:
https://patchwork.kernel.org/bundle/netdev/stable/?series=382773&state=*
Stefano