netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Samir Bellabes <sam@synack.fr>
To: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Cc: John Heffner <jheffner@psc.edu>,
	David Miller <davem@davemloft.net>,
	ilpo.jarvinen@helsinki.fi, netdev@vger.kernel.org
Subject: Re: TCP event tracking via netlink...
Date: Wed, 05 Dec 2007 16:12:46 +0100	[thread overview]
Message-ID: <m21wa118gh.fsf@synack.fr> (raw)
In-Reply-To: <20071205144843.GB2623@2ka.mipt.ru> (Evgeniy Polyakov's message of "Wed, 5 Dec 2007 17:48:43 +0300")

Evgeniy Polyakov <johnpol@2ka.mipt.ru> writes:

> Hi.
>
> On Wed, Dec 05, 2007 at 09:11:01AM -0500, John Heffner (jheffner@psc.edu) wrote:
>> >Maybe if we want to get really fancy we can have some more-expensive
>> >debug mode where detailed specific events get generated via some
>> >macros we can scatter all over the place.  This won't be useful
>> >for general user problem analysis, but it will be excellent for
>> >developers.
>> >
>> >Let me know if you think this is useful enough and I'll work on
>> >an implementation we can start playing with.
>> 
>> 
>> FWIW, sounds similar to what these guys are doing with SIFTR for FreeBSD:
>> http://caia.swin.edu.au/urp/newtcp/tools.html
>> http://caia.swin.edu.au/reports/070824A/CAIA-TR-070824A.pdf
>
> And even more similar to this patch from Samir Bellabes of Mandriva:
> http://lwn.net/Articles/202255/

Indeed, I was thinking about this idea. but yet, my goal is not to deal
with specific protocols like TCP, it's just to deal with the LSM hooks.
Anyway, the idea is the same, having a deamon is userspace to catch
informations. So why not a expansion? 

Lately, I'm moving the code to generic netlink, from connector.
regards,
sam

  reply	other threads:[~2007-12-05 15:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-05 13:30 TCP event tracking via netlink David Miller
2007-12-05 14:11 ` John Heffner
2007-12-05 14:48   ` Evgeniy Polyakov
2007-12-05 15:12     ` Samir Bellabes [this message]
2007-12-06  5:03     ` David Miller
2007-12-06 10:58       ` Evgeniy Polyakov
2007-12-06  5:00   ` David Miller
2007-12-05 16:53 ` Joe Perches
2007-12-05 21:33   ` Stephen Hemminger
2007-12-05 22:15     ` Ilpo Järvinen
2007-12-06  4:06       ` Stephen Hemminger
2007-12-06 10:20     ` David Miller
2007-12-06 13:28       ` Arnaldo Carvalho de Melo
2007-12-05 23:18 ` Ilpo Järvinen
2007-12-06 10:33   ` David Miller
2007-12-06 17:23     ` Stephen Hemminger
2007-12-07  6:51       ` David Miller
2008-01-02  8:22       ` David Miller
2008-01-02 11:05         ` Ilpo Järvinen
2008-01-03  9:26           ` David Miller
2007-12-07 16:43     ` Ilpo Järvinen

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=m21wa118gh.fsf@synack.fr \
    --to=sam@synack.fr \
    --cc=davem@davemloft.net \
    --cc=ilpo.jarvinen@helsinki.fi \
    --cc=jheffner@psc.edu \
    --cc=johnpol@2ka.mipt.ru \
    --cc=netdev@vger.kernel.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).