netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Damato <joe@boundary.com>
To: zbr@ioremap.net
Cc: netdev@vger.kernel.org, Joe Damato <joe@boundary.com>
Subject: [PATCH 0/2] connector: Add proc_events for connect/accept
Date: Mon,  1 Aug 2011 11:04:23 -0700	[thread overview]
Message-ID: <1312221865-3012-1-git-send-email-joe@boundary.com> (raw)

Hi -

It would be extremely useful to have a simple way of mapping pids to network
connections without having to create piles of inotify watches in /proc/ and
/proc/<pid>/fd/ and then search for corresponding inode numbers in
/proc/net/{tcp, udp, ... }.

I've added two simple connector events so that monitoring processes using
connector can get a notification of successful calls to connect/accept. This
allows a monitoring process to be aware of network connections without having
to jump through the inotify+proc parsing hoops.

Thanks,
Joe

Joe Damato (2):
  Create a new connector proc_event for successful calls to connect.
  Create a new connector proc_event for successful calls to accept.

 drivers/connector/cn_proc.c |   70 +++++++++++++++++++++++++++++++++++++++++++
 include/linux/cn_proc.h     |   39 +++++++++++++++++++++++-
 net/socket.c                |    9 +++++
 3 files changed, 117 insertions(+), 1 deletions(-)

-- 
1.7.4.1


             reply	other threads:[~2011-08-01 18:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-01 18:04 Joe Damato [this message]
2011-08-01 18:04 ` [PATCH 1/2] Create a new connector proc_event for successful calls to connect Joe Damato
2011-08-01 18:04 ` [PATCH 2/2] Create a new connector proc_event for successful calls to accept Joe Damato
2011-08-03 15:02   ` Samir Bellabes

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=1312221865-3012-1-git-send-email-joe@boundary.com \
    --to=joe@boundary.com \
    --cc=netdev@vger.kernel.org \
    --cc=zbr@ioremap.net \
    /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).