From: Stefan Hajnoczi <stefanha@redhat.com>
To: netdev@vger.kernel.org
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Jorgen Hansen <jhansen@vmware.com>,
Dexuan Cui <decui@microsoft.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: [PATCH iproute2 v2 0/3] ss: add AF_VSOCK support
Date: Fri, 6 Oct 2017 11:48:38 -0400 [thread overview]
Message-ID: <20171006154841.10495-1-stefanha@redhat.com> (raw)
v2:
* Use uint64_t instead of __u64 for filter->families
* Added reference to net-next commit that merged vsock_diag.ko
This patch series adds AF_VSOCK support to ss(8). AF_VSOCK is a host<->guest
communications channel supported by VMware, KVM (virtio-vsock), and Hyper-V.
To dump AF_VSOCK sockets:
$ ss --vsock
The vsock_diag.ko module has now been merged in the Linux net-next tree. I
have verified that the <linux/vm_sockets_diag.h> header copy in this patch
series is in sync with Linux net-next. See commit
5820299a271fd3dc9b1733e1e10cd7b983edd028 ("Merge branch 'VSOCK-sock_diag'").
Stefan Hajnoczi (3):
ss: allow AF_FAMILY constants >32
include: add <linux/vm_sockets_diag.h>
ss: add AF_VSOCK support
include/linux/vm_sockets_diag.h | 33 ++++++
misc/ss.c | 238 +++++++++++++++++++++++++++++++++++-----
man/man8/ss.8 | 8 +-
3 files changed, 249 insertions(+), 30 deletions(-)
create mode 100644 include/linux/vm_sockets_diag.h
--
2.13.6
next reply other threads:[~2017-10-06 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 15:48 Stefan Hajnoczi [this message]
2017-10-06 15:48 ` [PATCH iproute2 v2 1/3] ss: allow AF_FAMILY constants >32 Stefan Hajnoczi
2017-10-06 15:48 ` [PATCH iproute2 v2 2/3] include: add <linux/vm_sockets_diag.h> Stefan Hajnoczi
2017-10-06 15:48 ` [PATCH iproute2 v2 3/3] ss: add AF_VSOCK support Stefan Hajnoczi
2017-10-11 17:52 ` [PATCH iproute2 v2 0/3] " Stephen Hemminger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171006154841.10495-1-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=decui@microsoft.com \
--cc=jhansen@vmware.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.