From: Muli Ben-Yehuda <mulix@mulix.org>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: modules registering as sysctl handlers
Date: Tue, 2 Mar 2004 14:29:09 +0200 [thread overview]
Message-ID: <20040302122909.GG24260@mulix.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 488 bytes --]
Hi
Looking at 2.6.3-bk, it appears that the sysctl code does not raise a
module's reference count before calling a sysctl handler registered by
that module.
- are modules allowed to register sysctl handlers?
register_sysctl_table is exported, so I imagine so.
- am I missing something and modules are in fact protected against
concurrent unloading and invocation of sysctl?
Cheers,
Muli
--
Muli Ben-Yehuda
http://www.mulix.org | http://mulix.livejournal.com/
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-03-02 12:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-02 12:29 Muli Ben-Yehuda [this message]
2004-03-02 12:41 ` modules registering as sysctl handlers viro
2004-03-03 0:05 ` Rusty Russell
2004-03-03 9:22 ` Muli Ben-Yehuda
2004-03-03 10:43 ` viro
2004-03-04 10:38 ` Muli Ben-Yehuda
2004-03-04 13:59 ` Dave Jones
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=20040302122909.GG24260@mulix.org \
--to=mulix@mulix.org \
--cc=linux-kernel@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