search for: vmci_transport_stream_allow

...port.c > b/net/vmw_vsock/vmci_transport.c > index 644d32e43d23..4b8b1150a738 100644 > --- a/net/vmw_vsock/vmci_transport.c > +++ b/net/vmw_vsock/vmci_transport.c > @@ -648,7 +648,7 @@ static int vmci_transport_recv_dgram_cb(void *data, > struct vmci_datagram *dg) > static bool vmci_transport_stream_allow(u32 cid, u32 port) > { > static const u32 non_socket_contexts[] = { > - VMADDR_CID_RESERVED, > + VMADDR_CID_LOCAL, > }; > int i; > > -- > 2.21.0 Reviewed-by: Jorgen Hansen <jhansen at vmware.com>

v2: - style fixes [Dave] - removed RCU sync and changed 'the_vsock_loopback' in a global static variable [Stefan] - use G2H transport when local transport is not loaded and remote cid is VMADDR_CID_LOCAL [Stefan] - rebased on net-next v1: https://patchwork.kernel.org/cover/11251735/ This series introduces a new transport (vsock_loopback) to handle local communication. This

Hi, now that we have multi-transport upstream, I started to take a look to support network namespace (netns) in vsock. As we partially discussed in the multi-transport proposal [1], it could be nice to support network namespace in vsock to reach the following goals: - isolate host applications from guest applications using the same ports with CID_ANY - assign the same CID of VMs running in

Hi, now that we have multi-transport upstream, I started to take a look to support network namespace (netns) in vsock. As we partially discussed in the multi-transport proposal [1], it could be nice to support network namespace in vsock to reach the following goals: - isolate host applications from guest applications using the same ports with CID_ANY - assign the same CID of VMs running in