Bug 5270 - modprobe does not handle built-in modules
Summary: modprobe does not handle built-in modules
Status: RESOLVED FIXED
Alias: None
Product: Busybox
Classification: Unclassified
Component: Other (show other bugs)
Version: unspecified
Hardware: PC Linux
: P5 minor
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-02 15:27 UTC by Michael Tokarev
Modified: 2017-04-06 09:55 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:


Attachments
modprobe-read-modules-builtin.patch (1.95 KB, patch)
2012-08-12 18:30 UTC, Michael Tokarev
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Tokarev 2012-06-02 15:27:10 UTC
When busybox modprobe is asked to load a module which is built-in to the running kernel, it complains that the module isn't found:

# busybox modprobe unix
modprobe: module unix not found in modules.dep
# echo $?
1
# fgrep unix /lib/modules/$(uname -r)/modules.builtin
kernel/net/unix/unix.ko
# _


Upstream modprobe handles requests for insertion of such modules without returning error (except of --first-time case), just like for regular but already loaded modules.

This is debian bug #652672: http://bugs.debian.org/652672

Thanks,

/mjt
Comment 1 Michael Tokarev 2012-08-12 18:30:06 UTC
Created attachment 4490 [details]
modprobe-read-modules-builtin.patch

This patch from Ben Hutchings fixes the problem.  It only covers module loading, not unloading -- during unload, it will fail the same way as before.  I'm not sure it is worth to fix this however.
Comment 2 Denys Vlasenko 2017-04-06 09:55:15 UTC
Applied, thanks