Race condition in module load causing undefined symbols
in [Kernel]
|
Next: Am1771 wireless driver?
From: Prarit Bhargava on 15 Jun 2005 07:40 Pozsýr Balýzs wrote: > On Tue, Jun 14, 2005 at 02:23:04PM -0400, Prarit Bhargava wrote: > >>The second fix, and again you must do this if you're developing 2.6.12, is >>to *update the mkinitrd package* which has a new version of /bin/sh. > > > This sounds insane to me. I am using bash in my initrd, does this mean > that every shell and whatever has to be updated? Exactly what > modifications has to be made? > > If you're using bash, I would suggest starting with an update of the bash package. It's interesting to note that Steve also needed to update his udev package. Steve, IIRC you were using Fedora 3/4? P. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Pozsár Balázs on 15 Jun 2005 07:50 On Wed, Jun 15, 2005 at 07:35:22AM -0400, Prarit Bhargava wrote: > Pozsýr Balýzs wrote: > > >>If you're using bash, I would suggest starting with an update of the bash > >>package. > > > > > >Well, I'm using 3.0 and afaik there's no newer version, but I don't > >think this is the problem either. > > > >Exactlywhat modifications have to be made and to what to work around > >this kernel regression? > > > > Just to be clear, this isn't a kernel regression -- it's a problem with > packages ;). Let me this very clear: I've got a few initscripts written in bash, which load some modules. These are very basic and trivial straightforward, basically some "modprobe whatever". All works fine with 2.6.9. It does not work properly with 2.6.12-rc5. This is a regression. -- pozsy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Prarit Bhargava on 15 Jun 2005 07:50 Pozsýr Balýzs wrote: >>If you're using bash, I would suggest starting with an update of the bash >>package. > > > Well, I'm using 3.0 and afaik there's no newer version, but I don't > think this is the problem either. > > Exactlywhat modifications have to be made and to what to work around > this kernel regression? > Just to be clear, this isn't a kernel regression -- it's a problem with packages ;). Try backing out the patch I pointed to earlier in the thread. Let's see if that works... P. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Stephen Lord on 15 Jun 2005 08:40
Prarit Bhargava wrote: > > If you're using bash, I would suggest starting with an update of the > bash package. > > It's interesting to note that Steve also needed to update his udev > package. Steve, IIRC you were using Fedora 3/4? > > P. > I am running an updated Fedora Core 3 - on both machines which have the problem. I used rpms from Fedora Core 4 to update the system, this led to a chain of updates, mkinitrd, udev, initscripts and a few others with cross dependencies. Still puzzled about what could have been fixed in user space since this appears to affect more than one shell. Module loading appears to be very synchronous, so unless the shell was not waiting for exit status on children correctly, it seems hard to explain in user space. Steve - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |