All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Craig Gallek <kraig@google.com>
Cc: netdev@vger.kernel.org, edumazet@google.com, mleitner@redhat.com,
	stephen@networkplumber.org, davem@davemloft.net,
	ebiederm@xmission.net, tgraf@suug.ch, xemul@openvz.org
Subject: Re: [PATCH net-next 3/3] sock_diag: implement a get_info handler for inet
Date: Mon, 15 Jun 2015 13:30:56 -0700	[thread overview]
Message-ID: <1434400256.27504.145.camel@edumazet-glaptop2.roam.corp.google.com> (raw)
In-Reply-To: <1434381980-20588-4-git-send-email-kraig@google.com>

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@google.com>
> ---

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

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

Thanks Craig !

  reply	other threads:[~2015-06-15 20:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-15 15:26 [PATCH net-next 0/3] Socket destruction events via netlink sock_diag Craig Gallek
2015-06-15 15:26 ` [PATCH net-next 1/3] sock_diag: define destruction multicast groups Craig Gallek
2015-06-15 20:29   ` Eric Dumazet
2015-06-15 15:26 ` [PATCH net-next 2/3] sock_diag: specify info_size per inet protocol Craig Gallek
2015-06-15 20:29   ` Eric Dumazet
2015-06-15 15:26 ` [PATCH net-next 3/3] sock_diag: implement a get_info handler for inet Craig Gallek
2015-06-15 20:30   ` Eric Dumazet [this message]
2015-06-15 17:20 ` [PATCH net-next 0/3] Socket destruction events via netlink sock_diag Marcelo Ricardo Leitner
2015-06-15 20:28 ` Eric Dumazet
2015-06-16  2:49 ` David Miller

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=1434400256.27504.145.camel@edumazet-glaptop2.roam.corp.google.com \
    --to=eric.dumazet@gmail.com \
    --cc=davem@davemloft.net \
    --cc=ebiederm@xmission.net \
    --cc=edumazet@google.com \
    --cc=kraig@google.com \
    --cc=mleitner@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    --cc=tgraf@suug.ch \
    --cc=xemul@openvz.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.