On Thu, 1 Jan 2015 19:01:52 +0100 Denys Vlasenko <[email protected]> wrote:
> On Mon, Dec 29, 2014 at 2:29 PM, Natanael Copa <[email protected]> wrote: > > Hi, > > > > After upgrading to busybox-1.23 Alpine Linux boxes would no longer boot > > up and gave an initramfs emergency shell. > > > > The problem is commit 4e314faa0 (modprobe,rmmod: reject module names > > with slashes) which will exit with error if module name with slash is > > found. > > > > The problem with this is that there are some module aliases from > > kernel that contains slashes. dmi modules to be more exact. Since > > Alpine linux searches for 'modalias' in /sys and calls modprobe -a with > > all found aliases, it would stop loading modules when it came to dmi > > modalias with slash. This resulted in disk controller not beeing loaded. > > > > I added a local patch that disabled the slash check when option -a is > > specified, but I think that we should not abort on slash since > > modaliases can contain slashes. > > > > I suggest that we revert 4e314faa0 (modprobe,rmmod: reject module names > > with slashes) > > I looked at it and I think maybe the whole "remove basenamy" thingy is > an error, a leftover from needing to support "rmmod dir/name", > which now has its own basename stripping. > > Please try this: > > http://busybox.net/downloads/fixes-1.23.0/busybox-1.23.0-modprobe.patch > > and let me know whether it works for you. Sorry for late response. Seems like the last hunk in that patch breaks depmod completely. It works for me without the last hunk though. -nc _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
