From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Luca Pesce <pesce.luca@gmail.com>
Cc: Nils Rennebarth <Nils.Rennebarth@web.de>,
netfilter-devel@vger.kernel.org
Subject: Re: How to register conntrack notifier
Date: Thu, 12 Nov 2009 13:13:57 +0100 [thread overview]
Message-ID: <4AFBFC05.2000802@netfilter.org> (raw)
In-Reply-To: <873dce860911120252x6b00c4c6n564e09a88c341c19@mail.gmail.com>
Luca Pesce wrote:
> Hi Pablo,
> I was looking at conntrack events callbacks and conntrack tools too.
> As you said in your mail, only one callback can be registered, so if
> nf_conntrack_netlink module is loaded, no other modules can register a
> callback for events.
>
> If I correctly undertand the code, it seems that in the past kernels
> this limitation was not there.
Indeed. This limitation was introduced recently
> For example, 2.6.21.5 version had a
> notifier chain declared in nf_conntrack_ecache.c:
>
> ATOMIC_NOTIFIER_HEAD(nf_conntrack_chain);
>
> and nf_conntrack_register_notifier() simply adds an entry (callback
> block) to the chain, so many callbacks could be registered for
> conntrack events. Am I right?
Yes.
> Why has this been changed nowadays?
Because the notifier chain added too much overhead for the only single
client (nf_conntrack_netlink) in the kernel code.
next prev parent reply other threads:[~2009-11-12 11:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 15:03 How to register conntrack notifier Nils Rennebarth
2009-10-28 12:14 ` Pablo Neira Ayuso
2009-11-12 10:52 ` Luca Pesce
2009-11-12 12:13 ` Pablo Neira Ayuso [this message]
2009-11-13 8:39 ` Luca Pesce
2009-11-13 10:50 ` Pablo Neira Ayuso
2009-11-13 14:18 ` Luca Pesce
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=4AFBFC05.2000802@netfilter.org \
--to=pablo@netfilter.org \
--cc=Nils.Rennebarth@web.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pesce.luca@gmail.com \
/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.