linux-kernel - Re: [PATCH] xhci: Compute last_ctx from complete set of configured endpoints.

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:	Sun, 30 Jun 2013 14:08:16 -0700
From:	Sarah Sharp <sarah.a.sharp@...ux.intel.com>
To:	Reilly Grant <grantr@...are.com>
Cc:	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH] xhci: Compute last_ctx from complete set of configured
 endpoints.

On Mon, Jun 24, 2013 at 09:24:28AM -0700, Reilly Grant wrote:
> On Mon, Jun 24, 2013 at 08:59AM -0700, Sarah Sharp wrote:
> > On Tue, Jun 18, 2013 at 02:09:13PM -0700, Reilly Grant wrote:
> > 
> > So, no, I can't accept this patch.  If this fixes a real problem in
> > some hardware, we'll add a quirk for that hardware.
> 
> Thank you for the clarification. I was not aware of this addendum.
> Could you forward me a link to it? The last revision I can find on the
> Intel web site is from 05/2010.

The xHCI architect hasn't done an official release on the Intel site for
a while now.  I think he's working on a bigger 1.1 release that includes
all the errata over the past couple years.

I think you can get the latest revision by emailing
xhcisupport@...el.com.  If you don't hear back within a week or so,
email me back and I'll send you a PDF.

> This fixed a problem on VMware's virtual hardware. Assuming changing
> behavior will not affect any other systems I will fix it based on this
> information.

Yes, please fix this in VMware's virtual hardware.

Thanks,
Sarah Sharp
--
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/