From: Bobby Eshleman <bobby.eshle...@bytedance.com>

This commit implements datagram support for vsock loopback.

Not much more than simply toggling on "dgram_allow" and continuing to
use the common virtio functions.

Signed-off-by: Bobby Eshleman <bobby.eshle...@bytedance.com>
Signed-off-by: Amery Hung <amery.h...@bytedance.com>
---
 net/vmw_vsock/vsock_loopback.c | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/net/vmw_vsock/vsock_loopback.c b/net/vmw_vsock/vsock_loopback.c
index 4dd4886f29d1..0de4e2c8573c 100644
--- a/net/vmw_vsock/vsock_loopback.c
+++ b/net/vmw_vsock/vsock_loopback.c
@@ -46,6 +46,11 @@ static int vsock_loopback_cancel_pkt(struct vsock_sock *vsk)
        return 0;
 }
 
+static bool vsock_loopback_dgram_allow(u32 cid, u32 port)
+{
+       return true;
+}
+
 static bool vsock_loopback_seqpacket_allow(u32 remote_cid);
 static bool vsock_loopback_msgzerocopy_allow(void)
 {
@@ -66,7 +71,7 @@ static struct virtio_transport loopback_transport = {
                .cancel_pkt               = vsock_loopback_cancel_pkt,
 
                .dgram_enqueue            = virtio_transport_dgram_enqueue,
-               .dgram_allow              = virtio_transport_dgram_allow,
+               .dgram_allow              = vsock_loopback_dgram_allow,
 
                .stream_dequeue           = virtio_transport_stream_dequeue,
                .stream_enqueue           = virtio_transport_stream_enqueue,
-- 
2.20.1


Reply via email to