On Sun, 2016-01-24 at 13:22 -0800, Greg KH wrote:
> On Thu, Jan 21, 2016 at 03:18:48PM +0100, Oliver Neukum wrote:
> > Quting the relevant thread:
> >
> > > In fact, I suspect the locking added by the kernel 3.13 commit for
> > > read_descriptors() is invalid because read_descriptors() performs
On Thu, Jan 21, 2016 at 03:18:48PM +0100, Oliver Neukum wrote:
> Quting the relevant thread:
>
> > In fact, I suspect the locking added by the kernel 3.13 commit for
> > read_descriptors() is invalid because read_descriptors() performs no USB
> > activity; read_descriptors() just reads
On 21/01/16 14:18, Oliver Neukum wrote:
Quting the relevant thread:
In fact, I suspect the locking added by the kernel 3.13 commit for
read_descriptors() is invalid because read_descriptors() performs no USB
activity; read_descriptors() just reads information from an allocated
memory
On Thu, 21 Jan 2016, Oliver Neukum wrote:
> Quting the relevant thread:
>
> > In fact, I suspect the locking added by the kernel 3.13 commit for
> > read_descriptors() is invalid because read_descriptors() performs no USB
> > activity; read_descriptors() just reads information from an allocated
Quting the relevant thread:
> In fact, I suspect the locking added by the kernel 3.13 commit for
> read_descriptors() is invalid because read_descriptors() performs no USB
> activity; read_descriptors() just reads information from an allocated
> memory structure. This structure is protected as
