netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@gmail.com>
To: netdev@vger.kernel.org
Cc: stephen@networkplumber.org, avagin@openvz.org,
	Cyrill Gorcunov <gorcunov@gmail.com>
Subject: [PATCH net-next iproute2 0/2 v2] Add support for operating raw sockest via diag interface
Date: Wed,  2 Nov 2016 16:14:54 +0300	[thread overview]
Message-ID: <1478092496-7540-1-git-send-email-gorcunov@gmail.com> (raw)

The diag interface for raw sockets is now in linux-net-next
http://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=432490f9d455fb842d70219f22d9d2c812371676
so here is early patches for misc/ss

I've to update libnetlink code to keep backward compatibility and switch to
parse procfs output if no raw_diag module present in the system. Note the error
reporting sitting in the kernel since 2006 so it's not something new, I guess
this hasn't been done for other diag modules because it been assumed that they
are always here. Which is not applied to fresh raw-diag module.

	Cyrill
-- 
2.7.4

             reply	other threads:[~2016-11-02 13:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-02 13:14 Cyrill Gorcunov [this message]
2016-11-02 13:14 ` [PATCH net-next iproute2 1/2 v2] libnetlink: Add test for error code returned from netlink reply Cyrill Gorcunov
2016-11-02 13:14 ` [PATCH net-next iproute2 PATCH 2/2 v2] ss: Add inet raw sockets information gathering via netlink diag interface Cyrill Gorcunov
2016-11-02 21:24   ` David Ahern
2016-12-01 18:57   ` Stephen Hemminger
2016-12-01 19:13     ` Cyrill Gorcunov

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=1478092496-7540-1-git-send-email-gorcunov@gmail.com \
    --to=gorcunov@gmail.com \
    --cc=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).