Re: [PATCH v3 0/5] VSOCK: add sock_diag interface

[David Miller <davem@davemloft.net>]

From: Stefan Hajnoczi <stefanha@redhat.com>
Date: Thu,  5 Oct 2017 16:46:49 -0400

> v3:
>  * Rebased onto net-next/master and resolved Hyper-V transport conflict
> 
> v2:
>  * Moved tests to tools/testing/vsock/.  I was unable to put them in selftests/
>    because they require manual setup of a VMware/KVM guest.
>  * Moved to __vsock_in_bound/connected_table() to af_vsock.h
>  * Fixed local variable ordering in Patch 4
> 
> There is currently no way for userspace to query open AF_VSOCK sockets.  This
> means ss(8), netstat(8), and other utilities cannot display AF_VSOCK sockets.
> 
> This patch series adds the netlink sock_diag interface for AF_VSOCK.  Userspace
> programs sent a DUMP request including an sk_state bitmap to filter sockets
> based on their state (connected, listening, etc).  The vsock_diag.ko module
> replies with information about matching sockets.  This userspace ABI is defined
> in <linux/vm_sockets_diag.h>.
> 
> The final patch adds a test suite that exercises the basic cases.
> 
> Jorgen and Dexuan: I have only tested the virtio transport but this should also
> work for VMCI and Hyper-V.  Please give it a shot if you have time.

Series applied, thanks.