From: Patrick McHardy <kaber@trash.net>
To: Harald Welte <laforge@netfilter.org>
Cc: Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>,
Yasuyuki KOZAKAI <yasuyuki.kozakai@toshiba.co.jp>
Subject: Re: [PATCH] nf_conntrack port of conntrack-event-api
Date: Wed, 03 Aug 2005 23:50:01 +0200 [thread overview]
Message-ID: <42F13C09.6090106@trash.net> (raw)
In-Reply-To: <20050803213816.GA3819@rama.de.gnumonks.org>
Harald Welte wrote:
> Hi! I've just committed the following patch to the nf_conntrack branch
> of my netfilter-2.6.14 tree:
>
> [NETFILTER] port conntrack-events from ip_conntrack to nf_conntrack
>
> This adds a notifier chain based event mechanism for nf_conntrack state
> changes. As opposed to the previous implementations in patch-o-matic, we
> do no longer need a field in the skb to achieve this.
The event cache also needs the fixes I sent in the "atomic counter
underflow" thread two hours ago.
Regards
Patrick
next prev parent reply other threads:[~2005-08-03 21:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-03 21:38 [PATCH] nf_conntrack port of conntrack-event-api Harald Welte
2005-08-03 21:50 ` Patrick McHardy [this message]
2005-08-04 21:43 ` Harald Welte
2005-08-05 16:48 ` Harald Welte
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=42F13C09.6090106@trash.net \
--to=kaber@trash.net \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=yasuyuki.kozakai@toshiba.co.jp \
/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.