On Mon, Nov 07, 2005 at 09:31:57AM -0800, Greg KH wrote:
> On Mon, Nov 07, 2005 at 12:33:29PM +0100, Marco d'Itri wrote:
> > On Nov 06, Greg KH <[email protected]> wrote:
> >
> > > This seems to be a Debian issue for some odd reason, I suggest filing a
> > > bug against the udev package (or just tagging onto the existing bug for
> > > this problem, I've seen it in there already...)
> > The reason this is usually seen only on Debian systems is that I am the
> > first one who shipped an udev package which runs many parallel modprobe
> > commands, but this is a genuine kernel/modprobe bug.
>
> I'm pretty sure OpenSuSE 10.0 does the same thing, and I don't think
> anyone has reported the same kind of bugs there. Makes me wonder what
> is really happening here...
If module A depends on module B, and "modprobe A" and "modprobe B" are
run parallel, there is time window when module B is already listed in
/proc/modules, but not completely loaded/initialized, it is in the state
"Loading". At this point "modprobe A" checks /proc/modules if module B
is already loaded, but it does not take into account that it is in the
state "Loading" and not yet "Live". So it tries to load module A, but it
fails, because there are missing symbols because module A did not
register them yet.
--
pozsy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
