All of lore.kernel.org
 help / color / mirror / Atom feed
From: Max Kellermann <max@duempel.org>
To: netfilter-devel@lists.netfilter.org
Subject: Re: [RFC] h323 module unloading fix
Date: Wed, 9 Feb 2005 10:10:23 +0100	[thread overview]
Message-ID: <20050209091023.GA6830@roonstrasse.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0502090933250.2846@blackhole.kfki.hu>

On 2005/02/09 09:59, Jozsef Kadlecsik <kadlec@blackhole.kfki.hu> wrote:
> I like Patrick's idea. There are not so many modules wich rely on
> unregistered helpers, and we could retain backward compatibility in the
> API like in the attached (untested) patch. What do you think?

Calling an "evicting" function in a module destructor for something
which the netfilter core didn't even know about until now doesn't look
elegant to me. For me, to every destructing function, there must be a
prior constructor call.

There is no compatibility problem with Harald's/my solution. My
proposition allows the "register_helper" function to register
"disabled" helpers, meaning that you have to both register and
unregister the H.245 helper.

If we ever decide that it is required to register "disabled" helpers,
we don't have to change the API again, and it costs us near to nothing
to instruct that now.

It does not matter if "register_helper" ignores disabled helpers for
now, and "unregister_helper" works like the "evicting" function
Patrick proposed; we can change internals like this any time we want
without having to touch modules again.

Max

  reply	other threads:[~2005-02-09  9:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-08 14:59 [RFC] h323 module unloading fix Harald Welte
2005-02-08 15:26 ` Max Kellermann
2005-02-08 15:52   ` Harald Welte
2005-02-08 15:55     ` Max Kellermann
2005-02-08 23:10 ` Patrick McHardy
2005-02-09  8:24   ` Harald Welte
2005-02-09  8:59     ` Jozsef Kadlecsik
2005-02-09  9:10       ` Max Kellermann [this message]
2005-02-09 10:25         ` Jozsef Kadlecsik
2005-02-09 10:05       ` Harald Welte
2005-02-09 13:34     ` Patrick McHardy

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=20050209091023.GA6830@roonstrasse.net \
    --to=max@duempel.org \
    --cc=netfilter-devel@lists.netfilter.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 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.