From: Andrey Vagin <avagin@openvz.org>
To: netdev@vger.kernel.org
Cc: Pavel Emelyanov <xemul@parallels.com>,
Andrey Vagin <avagin@openvz.org>,
Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH 0/4] ss: Get netlink sockets info via sock-diag
Date: Thu, 21 Mar 2013 13:33:22 +0400 [thread overview]
Message-ID: <1363858406-1489-1-git-send-email-avagin@openvz.org> (raw)
In-Reply-To: <1363857669-19990-1-git-send-email-avagin@openvz.org>
Cc: Stephen Hemminger <stephen@networkplumber.org>
Andrey Vagin (4):
ss: handle socket diag request in a separate function
ss: create a frunction to print info about netlink sockets
ss: show destination address for netlink sockets
ss: Get netlink sockets info via sock-diag
include/linux/netlink_diag.h | 40 ++++++++
misc/ss.c | 235 +++++++++++++++++++++++++++++--------------
2 files changed, 198 insertions(+), 77 deletions(-)
create mode 100644 include/linux/netlink_diag.h
--
1.7.11.7
next prev parent reply other threads:[~2013-03-21 9:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 9:21 [PATCH 0/2] netlink: implement socket diag for netlink sockets Andrey Vagin
2013-03-21 9:21 ` [PATCH 1/2] net: prepare netlink code for netlink diag Andrey Vagin
2013-03-21 9:21 ` [PATCH 2/2] netlink: Diag core and basic socket info dumping Andrey Vagin
2013-03-21 11:46 ` Pavel Emelyanov
2013-03-21 12:52 ` Thomas Graf
2013-03-21 14:31 ` Andrew Vagin
2013-03-21 14:41 ` Thomas Graf
2013-03-21 9:33 ` Andrey Vagin [this message]
2013-03-21 9:33 ` [PATCH 1/4] ss: handle socket diag request in a separate function Andrey Vagin
2013-03-21 9:33 ` [PATCH 2/4] ss: create a function to print info about netlink sockets Andrey Vagin
2013-03-21 9:33 ` [PATCH 3/4] ss: show destination address for " Andrey Vagin
2013-03-21 9:33 ` [PATCH 4/4] ss: Get netlink sockets info via sock-diag Andrey Vagin
2013-03-21 17:00 ` [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=1363858406-1489-1-git-send-email-avagin@openvz.org \
--to=avagin@openvz.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=xemul@parallels.com \
/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).