linux-kernel - Re: [Linux-usb-users] OHCI root_port

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:	Tue, 09 Oct 2007 14:27:19 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	stern@...land.harvard.edu
Cc:	greg@...ah.com, david-b@...bell.net, linux-kernel@...r.kernel.org,
	linux-usb-users@...ts.sourceforge.net
Subject: Re: [Linux-usb-users] OHCI root_port_reset() deadly loop...

From: Alan Stern <stern@...land.harvard.edu>
Date: Tue, 9 Oct 2007 14:42:34 -0400 (EDT)

> On Tue, 9 Oct 2007, Greg KH wrote:
> 
> > > Anyway, it certainly would be easy enough to make port resets mutually
> > > exclusive with EHCI initialization.  That would work on any platform,
> > > PCI or not.
> > 
> > That's a good idea, any thoughts as to how to do this?  I think I can
> > find some Intel and Dell people who would be glad to test this out if
> > you have a proposed patch.
> 
> Here is a proposed patch.  I haven't tried running it, but it compiles 
> okay.

Are we sure that this is the only event that causes the conflicts between
the EHCI and it's companion virtual OHCI/UHCI host(s)?

Is there a chip reset done to the EHCI controller early during device
probe that could cause problems too?

I know it's grotty, but I definitely feel more comfortable with the
fix involving making sure EHCI loads and fully probes first.
-
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/