linux-kernel - Re: [REGRESSION] [nailed] USB boot failure: USB: EHCI: make ehci-pci a separate driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 13 Feb 2013 11:05:43 +0100
From:	Andreas Mohr <andi@...as.de>
To:	Andreas Mohr <andi@...as.de>
Cc:	initramfs@...r.kernel.org, Maximilian Attems <maks@...ian.org>,
	Greg KH <gregkh@...uxfoundation.org>,
	Alan Stern <stern@...land.harvard.edu>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-usb@...r.kernel.org
Subject: Re: [REGRESSION] [nailed] USB boot failure: USB: EHCI: make ehci-pci
 a separate driver

Indeed,
adding

ehci_pci

to /etc/initramfs-tools/modules and running

update-initramfs -u -k 3.7.0-rc5+

to get /boot/initrd.img-3.7.0-rc5+
of the formerly broken -rc5+ build corrected
manages to fix boot.

On Wed, Feb 13, 2013 at 08:44:09AM +0100, Andreas Mohr wrote:
>   (is there a way to cleanly provide the accurately updated list
>   from the kernel side? Or is there a scripted mechanism to at least extract
>   all required *dependee* modules from the list of the ones that we
>   already know of? That would have saved our a** here...)

Wouldn't have...
ehci-pci is the new top-level depender on ehci-hcd, not the other way
around.
Unfortunately such a change is even more insidious since one cannot pick
up the change in an automated manner (via dependency inspection).

A more automated yet KISS solution for initramfs dependency stuff would
be desireable if perhaps unfeasible.

Andreas Mohr
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/