linux-kernel - Re: 3.0-rc6: USB khubd deadlock when hub is powered down

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] [day] [month] [year] [list]

Date:	Fri, 8 Jul 2011 19:43:35 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Alan Stern <stern@...land.harvard.edu>
Cc:	Sarah Sharp <sarah.a.sharp@...ux.intel.com>,
	Greg KH <greg@...ah.com>, <linux-usb@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: 3.0-rc6: USB khubd deadlock when hub is powered down

On Jul 08 Alan Stern wrote:
> In general, adding support for USB-3.0 has been a tremendous job (of 
> which Sarah has done the lion's share of the work), involving not just 
> adding a new driver but also making significant changes to the 
> subsystem core.  Those changes have been sufficiently complicated that 
> things haven't settled down yet.
> 
> Particularly since it has now become clear that a key implementation
> decision (to allocate periodic bandwidth dynamically, as it is used,
> rather than statically) needs to be reversed.  The fan-out effects from
> this will require changes to several other drivers as well, and this is 
> all still in the design stage.  Thus, we are forced to limp along with 
> a hacky, not-entirely-correct implementation until everything can be 
> put right.  I don't expect this to happen quickly.

OK, fair enough.  I acknowledge that such a scope expansion at all layers
of the subsystem is a difficult undertaking.  Plus, you had working
patches that addressed my issue, even before I got around to report it.
-- 
Stefan Richter
-=====-==-== -=== -=---
http://arcgraph.de/sr/
--
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/