modprobe broken with recursive deps

[Gilles Espinasse]

Selon Timo Teräs <timo.teras at iki.fi>:

> Mike Frysinger wrote:
> > off hand, the last known working version is busybox 1.4.1.  i imagine it
> > worked with later versions, but that is the last one that is readily
> > accessible under my cross-compile setup that i can confirm.  all of 1.13.x+
> > seem to be broken.
> >
> > it's a simple config: start with allnoconfig, then just enable insmod,
> rmmod,
> > lsmod, and modprobe (linux-2.6 only).
> >
> > then with a simple dependency list:
> > .../snd-page-alloc.ko:
> > .../snd.ko: .../soundcore.ko
> > .../snd-timer.ko: .../snd.ko
> > .../soundcore.ko:
> > .../snd-pcm.ko: .../snd-timer.ko .../snd-page-alloc.ko .../snd.ko
> >
> > doing `modprobe` on any module that only has a dependency list <=1 level
> deep
> > works fine.  as soon as i try to modprobe anything deeper, modprobe fails
> to
> > act recursively.  so lets look at the case of `modprobe snd-pcm` ...
>
> This was intentional. It speeds up loading time and reduces memory
> requirements
> considerably.
>
> The proper thing is to have modules.dep to contain full dependency list on it
> for each module. The depmod should generate a file like that (if it doesn't
> it's a depmod bug). I think module-init-tools depmod does the same.
>
wich module-init-tools version?

I had issue with modules.dep generated by depmod module-init-tools v3.4.1 and
using busybox-1.13 mdoprobe.
Generating modules.dep from busybox depmod solve the issue.


Gilles