| 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
| ||
|
Message-ID: <20071009043909.GA4940@kroah.com> Date: Mon, 8 Oct 2007 21:39:09 -0700 From: Greg KH <greg@...ah.com> To: David Miller <davem@...emloft.net> Cc: david-b@...bell.net, linux-usb-users@...ts.sourceforge.net, linux-kernel@...r.kernel.org Subject: Re: OHCI root_port_reset() deadly loop... On Mon, Oct 08, 2007 at 08:42:36PM -0700, David Miller wrote: > From: David Brownell <david-b@...bell.net> > Date: Mon, 08 Oct 2007 20:34:12 -0700 > > > > However, when both OHCI and EHCI are built as modules (or, similarly > > > I guess, OHCI is built-in and EHCI is modular) there appears to be > > > nothing in userspace which makes sure EHCI gets loaded first. > > > > The old /etc/hotplug/usb.rc script made sure to load those modules > > in the correct order: EHCI first. > > I expected to find something cute attempting to handle this under > /etc/udev, I have failed so far :-) No, nothing cute in udev itself, but it seems that all distros that I know of have a "load these modules now" type setting in their init scripts that can be used here. I can't think of a way to enforce this load order on the modules themselves due to the fact that OHCI might not even be needed for EHCI devices on UHCI (Intel) based chipsets :( Can anyone else? thanks, greg k-h - 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/
Powered by blists - more mailing lists