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:	Fri, 21 Feb 2014 10:16:36 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Larry Finger <Larry.Finger@...inger.net>
cc:	linux-usb@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Jes Sorensen <Jes.Sorensen@...hat.com>
Subject: Re: Warning from USC core on kernel 3.13

On Thu, 20 Feb 2014, Larry Finger wrote:

> Alan,
> 
> The Lenovo Yogi 13 tablet comes with a Realtek RTL8723AU wireless device built 
> in. Realtek sent me a driver that I modified so that it would build on new 
> kernels, and created a GitHub repo so that it would be available to the 
> community. One of the users of this driver is reporting intermittent warnings 
> that say
> 
> WARNING: CPU: 1 PID: 0 at drivers/usb/core/urb.c:452 usb_submit_urb+0x205/0x5d0()
> usb 1-1.4: BOGUS urb xfer, pipe 3 != type 1
> 
> The full splat is available at http://pastebin.com/VcFPd4Yt.
> 
> As no other user has reported this problem, I think this is some kind of problem 
> with the wireless device or the adapter on this box. Even so, I would like to 
> know more about what is happening. In addition, Jes Sorensen at RedHat is 
> working on making the driver suitable for submission to the staging part of the 
> tree. Just in case other uses run into the problem, it would be good to know if 
> a fix is possible.
> 
> Can you suggest any addition logging for when this situation occurs? The user is 
> generating his own kernels, thus we can add any patches we want.

You probably don't need any additional logging.

The WARNING is telling you that the usb_read_interrupt_complete() 
routine in the 8723au driver called usb_submit_urb() with an incorrect 
pipe value.  The URB specified a BULK pipe, but the endpoint in 
question is actually an INTERRUPT endpoint.

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ