From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [netfilter-core] strict rejection of init -> core references causes problems
Date: Fri, 09 Jul 2004 18:36:35 +0000 [thread overview]
Message-ID: <16622.58803.909534.754777@napali.hpl.hp.com> (raw)
In-Reply-To: <16622.17154.117052.31601@napali.hpl.hp.com>
>>>>> On Fri, 9 Jul 2004 10:01:27 +0200, Harald Welte <laforge@netfilter.org> said:
Harald> Initially Rusty wrote the modules like this, and I very much
Harald> agree with this decision to not replicate the same code in
Harald> module_init() and _exit() functions. (which would have to be
Harald> kept in sync every time some item is added to the
Harald> initialization chain).
Seems to me the maintainance aspect could be taken care of with inline
functions. No?
>> it's common practice, I suppose we don't have much choice but to allow
>> calls from core to init sections again. Perhaps someone from the
>> netfilter team could comment?
Harald> I wuold very much appreciate if this was still possible in
Harald> the future.
We don't have much of a choice, but I think it would be worthwhile to
consider whether netfilter could avoid doing this in the future. It
really is very easy to make a mistake when allowing core->init calls.
--david
next prev parent reply other threads:[~2004-07-09 18:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-09 7:02 strict rejection of init -> core references causes problems David Mosberger
2004-07-09 8:01 ` [netfilter-core] " Harald Welte
2004-07-09 15:59 ` Luck, Tony
2004-07-09 18:36 ` David Mosberger [this message]
2004-07-09 18:46 ` Luck, Tony
2004-07-09 18:52 ` [netfilter-core] " Harald Welte
2004-07-09 19:19 ` Luck, Tony
2004-07-10 7:15 ` Harald Welte
2004-07-12 14:36 ` [netfilter-core] strict rejection of init -> core references Jean-Marc Saffroy
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=16622.58803.909534.754777@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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