netdev - Re: [PATCH net-next 3/3] sock_diag: implement a get

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1434400256.27504.145.camel@edumazet-glaptop2.roam.corp.google.com>
Date:	Mon, 15 Jun 2015 13:30:56 -0700
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Craig Gallek <kraig@...gle.com>
Cc:	netdev@...r.kernel.org, edumazet@...gle.com, mleitner@...hat.com,
	stephen@...workplumber.org, davem@...emloft.net,
	ebiederm@...ssion.net, tgraf@...g.ch, xemul@...nvz.org
Subject: Re: [PATCH net-next 3/3] sock_diag: implement a get_info handler
 for inet

On Mon, 2015-06-15 at 11:26 -0400, Craig Gallek wrote:
> This get_info handler will simply dispatch to the appropriate
> existing inet protocol handler.
> 
> This patch also includes a new netlink attribute
> (INET_DIAG_PROTOCOL).  This attribute is currently only used
> for multicast messages.  Without this attribute, there is no
> way of knowing the IP protocol used by the socket information
> being broadcast.  This attribute is not necessary in the 'dump'
> variant of this protocol (though it could easily be added)
> because dump requests are issued for specific family/protocol
> pairs.
> 
> Tested: ss -E (note, the -E option has not yet been merged into
> the upstream version of ss).
> 
> Signed-off-by: Craig Gallek <kraig@...gle.com>
> ---

Note to readers : This extension was discussed during web10g talk in
Ottawa.

Acked-by: Eric Dumazet <edumazet@...gle.com>

Thanks Craig !


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html