Thread (7 messages) flat view 7 messages, 2 authors, 2013-03-21

Re: [PATCH 3/3] netlink: Diag core and basic socket info dumping (v2)

From: David Miller <davem@davemloft.net>
Date: 2013-03-21 16:38:40
Also in: lkml

From: Andrey Vagin <redacted>
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 <redacted>
Cc: "David S. Miller" <davem@davemloft.net>
Cc: Eric Dumazet <edumazet@google.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: "Eric W. Biederman" <redacted>
Cc: Gao feng <redacted>
Cc: Thomas Graf <tgraf@suug.ch>
Signed-off-by: Andrey Vagin <redacted>
Applied to net-next
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help