vsock: add VMADDR_CID_LOCAL definition
authorStefano Garzarella <sgarzare@redhat.com>
Tue, 10 Dec 2019 10:43:03 +0000 (11:43 +0100)
committerDavid S. Miller <davem@davemloft.net>
Wed, 11 Dec 2019 23:01:23 +0000 (15:01 -0800)
The VMADDR_CID_RESERVED (1) was used by VMCI, but now it is not
used anymore, so we can reuse it for local communication
(loopback) adding the new well-know CID: VMADDR_CID_LOCAL.

Cc: Jorgen Hansen <jhansen@vmware.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Jorgen Hansen <jhansen@vmware.com>
Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
include/uapi/linux/vm_sockets.h
net/vmw_vsock/vmci_transport.c

index 68d57c5e99bc0a4314065d1055ba043f34375236..fd0ed7221645d9ebe8daf56052337e065e7188f7 100644 (file)
 
 #define VMADDR_CID_HYPERVISOR 0
 
-/* This CID is specific to VMCI and can be considered reserved (even VMCI
- * doesn't use it anymore, it's a legacy value from an older release).
+/* Use this as the destination CID in an address when referring to the
+ * local communication (loopback).
+ * (This was VMADDR_CID_RESERVED, but even VMCI doesn't use it anymore,
+ * it was a legacy value from an older release).
  */
 
-#define VMADDR_CID_RESERVED 1
+#define VMADDR_CID_LOCAL 1
 
 /* Use this as the destination CID in an address when referring to the host
  * (any process other than the hypervisor).  VMCI relies on it being 2, but
index 644d32e43d230a84963e5ea2fa68dbddfdfe4aee..4b8b1150a7388762be3669bc999ce5edd4f8f5f5 100644 (file)
@@ -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;