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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 1 Apr 2014 18:01:11 -0400 (EDT)
From:	Alan Stern <>
To:	Julius Werner <>
cc:	Sarah Sharp <>,
	Mathias Nyman <>,
	Greg Kroah-Hartman <>,
	"" <>,
	LKML <>,
	Vincent Palatin <>,
	Andrew Bresticker <>,
	Jim Lin <>
Subject: Re: [PATCH] usb: xhci: Correct last context entry calculation for
 Configure Endpoint

On Tue, 1 Apr 2014, Julius Werner wrote:

> >
> >
> > There's an xHCI spec ambiguity:  Does the last valid context entry refer
> > to the last valid endpoint context in the *input* device context or the
> > *output* device context?

It's not ambiguous at all. clearly states:

	A 'valid' Input Slot Context for a Configure Endpoint Command
	requires the Context Entries field to be initialized to the
	index of the last valid Endpoint Context that is defined by the
	_target configuration_.

(my emphasis).

Thus, if the current config has ep0, ep1, and ep2 and the command drops
ep1, the Context Entries field should be set to the index of ep2 since
that is the last valid Endpoint Context in the target config (which
has only ep0 and ep2).

Alan Stern

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists