From: David Miller <davem@davemloft.net>
To: kraig@google.com
Cc: netdev@vger.kernel.org, edumazet@google.com, mleitner@redhat.com,
stephen@networkplumber.org, ebiederm@xmission.net, tgraf@suug.ch,
xemul@openvz.org
Subject: Re: [PATCH net-next 0/3] Socket destruction events via netlink sock_diag
Date: Mon, 15 Jun 2015 19:49:39 -0700 (PDT) [thread overview]
Message-ID: <20150615.194939.99619876772139652.davem@davemloft.net> (raw)
In-Reply-To: <1434381980-20588-1-git-send-email-kraig@google.com>
From: Craig Gallek <kraig@google.com>
Date: Mon, 15 Jun 2015 11:26:17 -0400
> This series extends the netlink sock_diag interface to broadcast
> socket information as they are being destroyed. The current
> interface is poll based and can not be used to retreive information
> about sockets that are destroyed between poll intervals.
>
> Only inet sockets are broadcast in this implementation, but other
> families could easily be added as needed in the future.
>
> If this patch set is accepted, a follow-up patch to the ss utility
> in the iproute2 suite will also be submitted.
Series applied, thanks Craig.
prev parent reply other threads:[~2015-06-16 2:49 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
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 [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=20150615.194939.99619876772139652.davem@davemloft.net \
--to=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 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).