From: Andrey Vagin <avagin@openvz.org>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, Andrey Vagin <avagin@openvz.org>
Subject: [PATCH 0/4] ss: Get netlink sockets info via sock-diag (v2)
Date: Wed, 5 Jun 2013 12:41:57 +0400 [thread overview]
Message-ID: <1370421721-30814-1-git-send-email-avagin@openvz.org> (raw)
On Thu, Mar 21, 2013 at 10:00:25AM -0700, Stephen Hemminger wrote:
> Since this depends on functionality not in the upstream kernel.
> Resubmit this during the 3.10 merge window. At the start of the merge
> window, headers are synchronized with the kernel headers.
Netlink socket diag is in the upstream kernel since 3.10-rc1.
v2: Update kernel headers
Andrey Vagin (4):
ss: handle socket diag request in a separate function
ss: create a function to print info about netlink sockets
ss: show destination address for netlink sockets
ss: Get netlink sockets info via sock-diag (v2)
include/linux/netlink_diag.h | 52 ++++++++++
misc/ss.c | 242 +++++++++++++++++++++++++++++--------------
2 files changed, 216 insertions(+), 78 deletions(-)
create mode 100644 include/linux/netlink_diag.h
--
1.8.2
next reply other threads:[~2013-06-05 8:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 8:41 Andrey Vagin [this message]
2013-06-05 8:41 ` [PATCH 1/4] ss: handle socket diag request in a separate function Andrey Vagin
2013-06-05 8:41 ` [PATCH 2/4] ss: create a function to print info about netlink sockets Andrey Vagin
2013-06-05 8:42 ` [PATCH 3/4] ss: show destination address for " Andrey Vagin
2013-06-05 8:42 ` [PATCH 4/4] ss: Get netlink sockets info via sock-diag (v2) Andrey Vagin
2013-06-05 15:56 ` [PATCH 0/4] " 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=1370421721-30814-1-git-send-email-avagin@openvz.org \
--to=avagin@openvz.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).