Re: [PATCH] USB: legousbtower: Fix buffers on stack

Hello, I have tested it and it works great!!! Thank you very much!! I use nqc to test it and it has uploaded the firmware to the brick perfectly. [ 164.835935] usb 4-5: new low-speed USB device number 3 using ohci-pci [ 165.050272] usb 4-5: New USB device found, idVendor=0694,

Re: [PATCH v17 2/3] usb: USB Type-C connector class

On Fri, Apr 21, 2017 at 10:13 PM, Guenter Roeck wrote: > On Fri, Apr 21, 2017 at 07:57:52PM +0530, Rajaram R wrote: >> On Fri, Apr 21, 2017 at 1:16 AM, Badhri Jagan Sridharan >> wrote: >> > Thanks for the responses :) >> > >> > So seems like we have a plan.

Re: Regression - Linux 4.9: ums_eneub6250 broken: transfer buffer not dma capable - Trace

On Fri, 21 Apr 2017, Andreas Hartmann wrote: > Here it goes: > > [ 337.698916] usb 1-1.1: new high-speed USB device number 3 using ehci-pci > [ 337.808695] usb 1-1.1: New USB device found, idVendor=0cf2, idProduct=6250 > [ 337.808702] usb 1-1.1: New USB device strings: Mfr=1, Product=2, >

[PATCH v2] usb: misc: legousbtower: Fix buffers on stack

Allocate buffers on HEAP instead of STACK for local structures that are to be received using usb_control_msg(). Signed-off-by: Maksim Salau Tested-by: Alfredo Rafael Vicente Boix Cc: sta...@vger.kernel.org --- Changes in v2: * made checkpatch happy

[PATCH 1/1] usb: dwc3: keystone: check return value

Function devm_clk_get() returns an ERR_PTR when it fails. However, in function kdwc3_probe(), its return value is not checked, which may result in a bad memory access bug. This patch fixes the bug. Signed-off-by: Pan Bian --- drivers/usb/dwc3/dwc3-keystone.c | 4 1

[PATCH] usb: core: Warn if an URB's transfer_buffer is on stack

We see a large number of fixes to several drivers to remove the usage of on-stack buffers feeding into USB transfer functions. Make it easier to spot the offenders by adding a warning in usb_start_wait_urb() for urb->transfer_buffer to be located on the stack. Signed-off-by: Florian Fainelli

Re: usb: dwc2: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 146s

Hi, > Eric Anholt hat am 20. April 2017 um 20:54 geschrieben: > > > Stefan Wahren writes: > > > Hi, > > > >> Doug Anderson hat am 18. April 2017 um 22:41 > >> geschrieben: > >> > >> > >> It's hard to know for sure that all

Re: [PATCH] usb: core: Warn if an URB's transfer_buffer is on stack

On Sat, 22 Apr 2017, Florian Fainelli wrote: > We see a large number of fixes to several drivers to remove the usage of > on-stack buffers feeding into USB transfer functions. Make it easier to spot > the offenders by adding a warning in usb_start_wait_urb() for > urb->transfer_buffer to be