From: "Ed Swierk" <eswierk@arastra.com>
To: linux-kernel@vger.kernel.org
Cc: rusty@rustcorp.com.au
Subject: [RETRY] [PATCH] load_module: no BUG if module_subsys uninitialized
Date: Fri, 22 Sep 2006 12:48:48 -0700 [thread overview]
Message-ID: <c1bf1cf0609221248v39113875id4b48c62cec8eb46@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
[I discovered after sending my previous message that Gmail helpfully
line-wrapped and de-tabified my patch. I'm resending it as an
attachment; apologies for the error.]
Invoking load_module() before param_sysfs_init() is called crashes in
mod_sysfs_setup(), since the kset in module_subsys is not initialized
yet.
Another patch for the same symptom
(module_subsys-initialize-earlier.patch) moves param_sysfs_init() to
the subsys initcalls, but this is still not early enough in the boot
process in some cases. In particular, topology_init() causes
/sbin/hotplug to run, which requests net-pf-1 (the UNIX socket
protocol) which can be compiled as a module. Moving param_sysfs_init()
to the postcore initcalls fixes this particular race, but there might
well be other cases where a usermodehelper causes a module to load
earlier still.
The patch below makes load_module() return an error rather than
crashing the kernel if invoked before module_subsys is initialized.
[-- Attachment #2: module_subsys-uninit-return-err.patch --]
[-- Type: text/x-patch, Size: 465 bytes --]
--- linux-2.6.17.11.orig/kernel/module.c 2006-08-23 21:16:33.000000000 +0000
+++ linux-2.6.17.11/kernel/module.c 2006-09-22 05:19:03.000000000 +0000
@@ -998,6 +998,12 @@
{
int err;
+ if (!module_subsys.kset.subsys) {
+ printk(KERN_ERR "%s: module_subsys not initialized\n",
+ mod->name);
+ err = -EINVAL;
+ goto out;
+ }
memset(&mod->mkobj.kobj, 0, sizeof(mod->mkobj.kobj));
err = kobject_set_name(&mod->mkobj.kobj, "%s", mod->name);
if (err)
next reply other threads:[~2006-09-22 19:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 19:48 Ed Swierk [this message]
2006-09-22 20:16 ` Greg KH
2006-09-22 21:28 ` Ed Swierk
2006-09-27 4:56 ` Greg KH
2006-09-27 19:10 ` Ed Swierk
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=c1bf1cf0609221248v39113875id4b48c62cec8eb46@mail.gmail.com \
--to=eswierk@arastra.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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
all inboxes | Powered by JetHome®