diff options
| author | Ed Swierk <[email protected]> | 2006-09-25 23:25:36 +0000 |
|---|---|---|
| committer | Linus Torvalds <[email protected]> | 2006-09-26 00:38:36 +0000 |
| commit | 1cc5f7142eca352109895fe20b1fc6405dd17727 (patch) | |
| tree | 9c6b4b3204f06317c830457e091ff2c83272ea09 /fs/jbd/commit.c | |
| parent | [PATCH] i386: fix flat mode numa on a real numa system (diff) | |
| download | kernel-1cc5f7142eca352109895fe20b1fc6405dd17727.tar.gz kernel-1cc5f7142eca352109895fe20b1fc6405dd17727.zip | |
[PATCH] load_module: no BUG if module_subsys uninitialized
Invoking load_module() before param_sysfs_init() is called crashes in
mod_sysfs_setup(), since the kset in module_subsys is not initialized yet.
In my case, net-pf-1 is getting modprobed as a result of hotplug trying to
create a UNIX socket. Calls to hotplug begin after the topology_init
initcall.
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 makes load_module() return an error rather than crashing the
kernel if invoked before module_subsys is initialized.
Cc: Mark Huang <[email protected]>
Cc: Greg KH <[email protected]>
Cc: <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'fs/jbd/commit.c')
0 files changed, 0 insertions, 0 deletions
