| 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: <200809121628.59900.david-b@pacbell.net> Date: Fri, 12 Sep 2008 16:28:59 -0700 From: David Brownell <david-b@...bell.net> To: Alan Stern <stern@...land.harvard.edu> Cc: Steven Noonan <steven.noonan@...inklabs.net>, Andrew Morton <akpm@...ux-foundation.org>, Kernel development list <linux-kernel@...r.kernel.org>, Steven Noonan <steven@...inklabs.net>, USB list <linux-usb@...r.kernel.org> Subject: Re: [PATCH 1/1] drivers/usb/host/pci-quirks.c: wait for EHCI handoff far too long in quirk_usb_disable_ehci() On Tuesday 09 September 2008, Alan Stern wrote: > > > > > > The delay in the current version of pci-quirks.c is 5 seconds, > > > which I've cut down to 0.5 seconds. > > > I guess it risks breaking someone else's system. Or perhaps the number > > was just grabbed out of the air. > > As far as I know, it was indeed just grabbed out of the air. The spec > specifically avoids giving an upper limit on how long to wait. > > > Can we do a separate quirk just for that machine (and ones with the > > same bug)? > > My BIOS has the same bug. I wouldn't mind seeing the delay reduced. I'm fairly sure that someone's system needed more than 1/2 second. And that going from 500 to 5000 was the obvious "add a zero" way to get to a long-enough timeout. -- 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