diff options
| author | David S. Miller <davem@davemloft.net> | 2017-10-05 18:44:18 -0700 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2017-10-05 18:44:18 -0700 |
| commit | 5820299a271fd3dc9b1733e1e10cd7b983edd028 (patch) | |
| tree | 88a8efdc3dcba52ab1d0e379a709d4043acbc6c7 /scripts/gdb/linux/cpus.py | |
| parent | 53954cf8c5d205624167a2bfd117cc0c1a5f3c6d (diff) | |
| parent | 0b02503384301e4c2db13f1045a1ddbaca2ba0ce (diff) | |
Merge branch 'VSOCK-sock_diag'
Stefan Hajnoczi says:
====================
VSOCK: add sock_diag interface
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.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'scripts/gdb/linux/cpus.py')
0 files changed, 0 insertions, 0 deletions
