From: David Miller <davem@davemloft.net>
To: avagin@openvz.org
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
xemul@parallels.com, edumazet@google.com, pablo@netfilter.org,
ebiederm@xmission.com, gaofeng@cn.fujitsu.com, tgraf@suug.ch
Subject: Re: [PATCH 3/3] netlink: Diag core and basic socket info dumping (v2)
Date: Thu, 21 Mar 2013 12:38:35 -0400 (EDT) [thread overview]
Message-ID: <20130321.123835.105179567859494344.davem@davemloft.net> (raw)
In-Reply-To: <1363883628-7249-4-git-send-email-avagin@openvz.org>
From: Andrey Vagin <avagin@openvz.org>
Date: Thu, 21 Mar 2013 20:33:48 +0400
> The netlink_diag can be built as a module, just like it's done in
> unix sockets.
>
> The core dumping message carries the basic info about netlink sockets:
> family, type and protocol, portis, dst_group, dst_portid, state.
>
> Groups can be received as an optional parameter NETLINK_DIAG_GROUPS.
>
> Netlink sockets cab be filtered by protocols.
>
> The socket inode number and cookie is reserved for future per-socket info
> retrieving. The per-protocol filtering is also reserved for future by
> requiring the sdiag_protocol to be zero.
>
> The file /proc/net/netlink doesn't provide enough information for
> dumping netlink sockets. It doesn't provide dst_group, dst_portid,
> groups above 32.
>
> v2: fix NETLINK_DIAG_MAX. Now it's equal to the last constant.
>
> Acked-by: Pavel Emelyanov <xemul@parallels.com>
> Cc: "David S. Miller" <davem@davemloft.net>
> Cc: Eric Dumazet <edumazet@google.com>
> Cc: Pablo Neira Ayuso <pablo@netfilter.org>
> Cc: "Eric W. Biederman" <ebiederm@xmission.com>
> Cc: Gao feng <gaofeng@cn.fujitsu.com>
> Cc: Thomas Graf <tgraf@suug.ch>
> Signed-off-by: Andrey Vagin <avagin@openvz.org>
Applied to net-next
prev parent reply other threads:[~2013-03-21 16:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 16:33 [PATCH 0/3] netlink: implement socket diag for netlink sockets (v2) Andrey Vagin
2013-03-21 16:33 ` [PATCH 1/3] net: fix *_DIAG_MAX constants Andrey Vagin
2013-03-21 16:37 ` David Miller
2013-03-21 16:33 ` [PATCH 2/3] net: prepare netlink code for netlink diag Andrey Vagin
2013-03-21 16:38 ` David Miller
2013-03-21 16:33 ` [PATCH 3/3] netlink: Diag core and basic socket info dumping (v2) Andrey Vagin
2013-03-21 16:38 ` David Miller [this message]
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=20130321.123835.105179567859494344.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=avagin@openvz.org \
--cc=ebiederm@xmission.com \
--cc=edumazet@google.com \
--cc=gaofeng@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=tgraf@suug.ch \
--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
all inboxes | Powered by JetHome®