netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vadim Kochan <vadim4j@gmail.com>
To: netdev@vger.kernel.org
Cc: Vadim Kochan <vadim4j@gmail.com>
Subject: [PATCH iproute2] ss: Identify a lot of netlink protocol names
Date: Thu, 16 Oct 2014 19:46:58 +0300	[thread overview]
Message-ID: <1413478018-12373-1-git-send-email-vadim4j@gmail.com> (raw)

There were only few Netlink protocol names:

    rtnl, fw, tcpdiag

which were printed on output.
So added the other ones.

Signed-off-by: Vadim Kochan <vadim4j@gmail.com>
---
 misc/ss.c | 61 +++++++++++++++++++++++++++++++++++++++++++++++++++++++------
 1 file changed, 55 insertions(+), 6 deletions(-)

diff --git a/misc/ss.c b/misc/ss.c
index 2420b51..576db4e 100644
--- a/misc/ss.c
+++ b/misc/ss.c
@@ -2960,12 +2960,63 @@ static int packet_show(struct filter *f)
 	return 0;
 }
 
+static char *netlink_proto_name(int proto)
+{
+	switch (proto)
+	{
+	case NETLINK_ROUTE:
+		return "rtnl";
+	case NETLINK_USERSOCK:
+		return "user";
+	case NETLINK_FIREWALL:
+		return "fw";
+	case NETLINK_SOCK_DIAG:
+		return "tcpdiag";
+	case NETLINK_NFLOG:
+		return "nflog";
+	case NETLINK_XFRM:
+		return "xfrm";
+	case NETLINK_SELINUX:
+		return "selinux";
+	case NETLINK_ISCSI:
+		return "iscsi";
+	case NETLINK_AUDIT:
+		return "audit";
+	case NETLINK_FIB_LOOKUP:
+		return "fiblookup";
+	case NETLINK_CONNECTOR:
+		return "conn";
+	case NETLINK_NETFILTER:
+		return "nft";
+	case NETLINK_IP6_FW:
+		return "ip6fw";
+	case NETLINK_DNRTMSG:
+		return "decrt";
+	case NETLINK_KOBJECT_UEVENT:
+		return "uevent";
+	case NETLINK_GENERIC:
+		return "genl";
+	case NETLINK_SCSITRANSPORT:
+		return "scsitrans";
+	case NETLINK_ECRYPTFS:
+		return "ecryptfs";
+	case NETLINK_RDMA:
+		return "rdma";
+	case NETLINK_CRYPTO:
+		return "crypto";
+	}
+
+	return NULL;
+};
+
 static void netlink_show_one(struct filter *f,
 				int prot, int pid, unsigned groups,
 				int state, int dst_pid, unsigned dst_group,
 				int rq, int wq,
 				unsigned long long sk, unsigned long long cb)
 {
+	char *prot_name;
+
 	if (f->f) {
 		struct tcpstat tst;
 		tst.local.family = AF_NETLINK;
@@ -2983,14 +3034,12 @@ static void netlink_show_one(struct filter *f,
 	if (state_width)
 		printf("%-*s ", state_width, "UNCONN");
 	printf("%-6d %-6d ", rq, wq);
-	if (resolve_services && prot == 0)
-		printf("%*s:", addr_width, "rtnl");
-	else if (resolve_services && prot == 3)
-		printf("%*s:", addr_width, "fw");
-	else if (resolve_services && prot == 4)
-		printf("%*s:", addr_width, "tcpdiag");
+
+	if (resolve_services && (prot_name = netlink_proto_name(prot)))
+		printf("%*s:", addr_width, prot_name);
 	else
 		printf("%*d:", addr_width, prot);
+
 	if (pid == -1) {
 		printf("%-*s ", serv_width, "*");
 	} else if (resolve_services) {
-- 
2.1.0

             reply	other threads:[~2014-10-16 16:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-16 16:46 Vadim Kochan [this message]
2014-10-30  5:49 ` [PATCH iproute2] ss: Identify a lot of netlink protocol names Stephen Hemminger
2014-10-30 15:26   ` vadim4j

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=1413478018-12373-1-git-send-email-vadim4j@gmail.com \
    --to=vadim4j@gmail.com \
    --cc=netdev@vger.kernel.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).