[PATCH net,stable v2] net: cdc_ncm: update datagram size after changing mtu

so it takes max_datagram_size with use of cdc_ncm_max_dgram_size() and not ctx. Signed-off-by: Robert Dobrowolski Signed-off-by: Rafal Redzimski --- Changes in v2: - Changed the way maxmtu is being calculated. Its now based on cdc_ncm_max_dgram_size and not on ctx->max_datagram_size. New datag

Re: [PATCH v1] net: cdc_ncm: update datagram size after changing mtu

> Robert Dobrowolski writes: > >> From: Rafal Redzimski >> >> Current implementation updates the mtu size and notify cdc_ncm >> device using USB_CDC_SET_MAX_DATAGRAM_SIZE request about datagram >> size change instead of changing rx_urb_size. >> >&

[PATCH v1] net: cdc_ncm: update datagram size after changing mtu

Redzimski Signed-off-by: Robert Dobrowolski --- drivers/net/usb/cdc_ncm.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/net/usb/cdc_ncm.c b/drivers/net/usb/cdc_ncm.c index 2fb31ed..4a47656 100644 --- a/drivers/net/usb/cdc_ncm.c +++ b/drivers/net/usb/cdc_ncm.c @@ -746,6 +746,8 @@ int

[PATCH v3] usb: hcd: out of bounds access in for_each_companion

From: Robert Dobrowolski On BXT platform Host Controller and Device Controller figure as same PCI device but with different device function. HCD should not pass data to Device Controller but only to Host Controllers. Checking if companion device is Host Controller, otherwise skip. Cc: Signed

[PATCH v4] usb: xhci: applying XHCI_PME_STUCK_QUIRK to Intel BXT B0 host

From: Rafal Redzimski Broxton B0 also requires XHCI_PME_STUCK_QUIRK. Adding PCI device ID for Broxton B and adding to quirk. Cc: Signed-off-by: Rafal Redzimski Signed-off-by: Robert Dobrowolski --- Changes in v4: - Updating commit message Changes in v3: - Corrected cc list Changes in v2

[PATCH v3] usb: xhci: applying XHCI_PME_STUCK_QUIRK to Intel BXT B0 host

From: Rafal Redzimski Broxton B0 also requires XHCI_PME_STUCK_QUIRK. Adding PCI device ID for Broxton B and adding to quirk. Signed-off-by: Rafal Redzimski Signed-off-by: Robert Dobrowolski --- Changes in v3: - Corrected cc list Changes in v2: - Fixed commit message drivers/usb/host/xhci

Re: [PATCH v2] usb: xhci: applying XHCI_PME_STUCK_QUIRK to Intel BXT B0 host

> On Wed, Mar 23, 2016 at 04:41:02AM -0700, Robert Dobrowolski wrote: >> From: Rafal Redzimski >> >> Broxton B0 also requires XHCI_PME_STUCK_QUIRK. >> Adding PCI device ID for Broxton B and adding to quirk. >> >> Signed-off-by: Rafal Redzimsk

[PATCH v2] usb: xhci: applying XHCI_PME_STUCK_QUIRK to Intel BXT B0 host

From: Rafal Redzimski Broxton B0 also requires XHCI_PME_STUCK_QUIRK. Adding PCI device ID for Broxton B and adding to quirk. Signed-off-by: Rafal Redzimski Signed-off-by: Robert Dobrowolski --- drivers/usb/host/xhci-pci.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a

[PATCH v1] usb: xhci: applying XHCI_PME_STUCK_QUIRK to Intel BXT B0 host

From: Rafal Redzimski Signed-off-by: Rafal Redzimski --- drivers/usb/host/xhci-pci.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/usb/host/xhci-pci.c b/drivers/usb/host/xhci-pci.c index f0640b7..071b34a 100644 --- a/drivers/usb/host/xhci-pci.c +++ b/drivers/usb

[PATCH v2] usb: hcd: out of bounds access in for_each_companion

On BXT platform Host Controller and Device Controller figure as same PCI device but with different device function. HCD should not pass data to Device Controller but only to Host Controllers. Checking if companion device is Host Controller, otherwise skip. Signed-off-by: Robert Dobrowolski

[PATCH v1] usb: hcd: out of bounds access in for_each_companion

On BXT platform Host Controller and Device Controller figure as same PCI device but with different device function. HCD should not pass data to Device Controller. Checking if companion device is Device Controller and omitting it. Signed-off-by: Robert Dobrowolski --- drivers/usb/core/hcd-pci.c