linux-kernel - Re: [ 12/75] USB: EHCI: work around silicon bug in Intels EHCI controllers

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]

Message-ID: <Pine.LNX.4.44L0.1303211034350.1899-100000@iolanthe.rowland.org>
Date:	Thu, 21 Mar 2013 10:35:31 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
cc:	Sven Joachim <svenjoac@....de>, <linux-kernel@...r.kernel.org>,
	<stable@...r.kernel.org>, Stephen Thirlwall <sdt@...com>
Subject: Re: [ 12/75] USB: EHCI: work around silicon bug in Intels EHCI
 controllers

On Wed, 20 Mar 2013, Greg Kroah-Hartman wrote:

> On Wed, Mar 20, 2013 at 04:41:21PM -0400, Alan Stern wrote:
> > On Wed, 20 Mar 2013, Greg Kroah-Hartman wrote:
> > 
> > > > > Ok, I'll postpone this patch for the next stable release, in time for
> > > > > the fix to be put in at the same time.
> > > > 
> > > > I think patch 13/75 ("USB: EHCI: dont check DMA values in QH overlays")
> > > > should also be postponed then, at least Alan said so in
> > > > <Pine.LNX.4.44L0.1303191125100.15684-100000@...rider.rowland.org>.
> > > 
> > > Crap, I didn't postpone that one, hopefully it doesn't cause as many
> > > problems...
> > 
> > I haven't tested this combination of changes, except in a highly 
> > artificial setting (i.e., running the usbtest suite), so I don't know 
> > how it will behave under normal use.  In any case, it's too late to do 
> > anything now except issue another -stable release.
> > 
> > I just saw that the "dont check DMA values" patch did get into the
> > 3.0-stable and 3.4-stable releases.  I didn't realize at the time, but
> > it shouldn't be in any kernel earlier than 3.6.  I guess the best thing
> > to do is queue up a reversion for those two series.
> 
> I've now done this, thanks.

Sorry I didn't catch those things at the time.  I should have been 
looking more closely at your -stable queue.

Alan Stern

--
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/