From: Samir Bellabes <sam@synack.fr>
To: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Cc: netdev@vger.kernel.org
Subject: Re: [RFC] [PATCH] Network Events Connector
Date: Thu, 15 Mar 2007 01:53:37 +0100 [thread overview]
Message-ID: <m2veh35nu6.fsf@cerbere.dyndns.info> (raw)
In-Reply-To: <20070217163422.GB22369@2ka.mipt.ru> (Evgeniy Polyakov's message of "Sat, 17 Feb 2007 19:34:22 +0300")
Evgeniy Polyakov <johnpol@2ka.mipt.ru> writes:
> On Fri, Feb 09, 2007 at 05:43:14AM +0100, Samir Bellabes (sam@synack.fr) wrote:
>> Hi,
>>
>> Here is a new feature which can help firewalls to be more application
>> aware, so more useful for people.
>>
>> Our previous discussion about cn_net and firewalls:
>> http://marc2.theaimsgroup.com/?t=115976957500002&r=1&w=2
>>
>> Please, I would really like to have feedback and comments on that tool,
>> in order to improve it.
>
> Technical side does have problems.
> 4. are you 100% sure there are misalignments and 32/64 bit userspace
> problems? you seems to copy some bits from proc connector, which
> suffered from that errors in the past.
No, i'm currently not sure of that.
I think you are refering to this :
http://git.kernel.org/?p=linux/kernel/git/acme/net-2.6.22.git;a=commitdiff;h=af3e095a1fb42bac32355d5d59ce93f8b4e59a3e
I'm going to care of this for cn_net
Evgeniy, thanks a lot for your review.
next prev parent reply other threads:[~2007-03-15 0:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 4:43 [RFC] [PATCH] Network Events Connector Samir Bellabes
2007-02-17 16:34 ` Evgeniy Polyakov
2007-03-15 0:48 ` Samir Bellabes
2007-03-15 0:50 ` Samir Bellabes
2007-03-15 0:53 ` Samir Bellabes [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-15 1:05 Samir Bellabes
2007-03-15 1:17 ` David Miller
2007-03-15 18:00 ` Evgeniy Polyakov
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=m2veh35nu6.fsf@cerbere.dyndns.info \
--to=sam@synack.fr \
--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).