usbip_host_driver.h now depends on several additional headers, which
need to be installed along with it.
Fixes: 021aed845303 ("staging: usbip: userspace: migrate usbip_host_driver ...")
Fixes: 3391ba0e2792 ("usbip: tools: Extract generic code to be shared with ...")
Signed-off-by: Ben Hutchings
-
On Sat, Sep 30, 2017 at 1:15 AM, Dan Carpenter wrote:
> There used to be a test against "if (param->sglen > MAX_SGLEN)" but it
> was removed during a refactor. It leads to an integer overflow and a
> stack overflow in test_queue() if we try to create a too large urbs[]
> array on the stack.
>
> T
On 09/29/2017 07:22 AM, Amelie DELAUNAY wrote:
> Hi,
>
> Gentle ping for driver review submitted on August 28th.
>
> Thanks,
> Amelie
>
> On 08/28/2017 04:20 PM, Amelie Delaunay wrote:
>> This patch adds the dwc2_set_params function for STM32F7 USB OTG HS.
>>
>> Signed-off-by: Amelie Delaunay
>> -
On 09/20/2017 12:57 PM, John Stultz wrote:
> So here are a few dwc2 fixes that I've been using with HiKey.
> I'm not totally sure these are all ideal, but they avoid edge case
> issues that we have been running into with switching between
> gadget mode and host mode.
>
> I'd guess the first two are
KASAN enabled configuration reports an error
BUG: KASAN: use-after-free in usb_composite_overwrite_options+...
[libcomposite] at addr ...
Read of size 1 by task ...
when some driver is un-bound and then bound again.
For example, this happens with FunctionFS driver when "ff
Kmemleak checking configuration reports a memory leak in
usb_os_desc_prepare_interf_dir function when rndis function
instance is freed and then allocated again. For example, this
happens with FunctionFS driver with RNDIS function enabled
when "ffs-test" test application is run several times in a ro
Hello!
On 9/28/2017 3:17 AM, Chunfeng Yun wrote:
When fail to get irq number, platform_get_irq() may return
Failing. IRQ. :-)
-EPROBE_DEFER, but we ignore it and always return -ENODEV,
so fix it.
Signed-off-by: Chunfeng Yun
---
drivers/usb/mtu3/mtu3_core.c |4 ++--
1 file change
On Fri, 29 Sep 2017 09:06:16 +
David Laight wrote:
> > The correct names used in the new specification for the 4 speeds that can
> > be supported by a USB 3
> > interface are: .
>
> I think I'd add the speed itself as well.
>
> David
I was reffering mostly to the identifiers and co
There used to be a test against "if (param->sglen > MAX_SGLEN)" but it
was removed during a refactor. It leads to an integer overflow and a
stack overflow in test_queue() if we try to create a too large urbs[]
array on the stack.
There is a second integer overflow in test_queue() as well if
"para