linux-stable.git/tools/usb/usbip/libsrc, branch linux-4.19.y

usbip: tools: fix build error for multiple definition

2021-03-11T13:04:59+00:00

commit d5efc2e6b98fe661dbd8dd0d5d5bfb961728e57a upstream.

With GCC 10, building usbip triggers error for multiple definition
of 'udev_context', in:
- libsrc/vhci_driver.c:18 and
- libsrc/usbip_host_common.c:27.

Declare as extern the definition in libsrc/usbip_host_common.c.

Signed-off-by: Antonio Borneo 
Acked-by: Shuah Khan 
Link: https://lore.kernel.org/r/20200618000844.1048309-1-borneo.antonio@gmail.com
Cc: Petr Štetiar 
Signed-off-by: Greg Kroah-Hartman

usbip: tools: fix fd leakage in the function of read_attr_usbip_status

2019-12-01T08:17:40+00:00

commit 26a4d4c00f85cb844dd11dd35e848b079c2f5e8f upstream.

We should close the fd before the return of read_attr_usbip_status.

Fixes: 3391ba0e2792 ("usbip: tools: Extract generic code to be shared with vudc backend")
Signed-off-by: Hewenliang 
Cc: stable 
Link: https://lore.kernel.org/r/20191025043515.20053-1-hewenliang4@huawei.com
Signed-off-by: Greg Kroah-Hartman

usbip: tools: fix atoi() on non-null terminated string

2019-12-01T08:16:38+00:00

[ Upstream commit e325808c0051b16729ffd472ff887c6cae5c6317 ]

Currently the call to atoi is being passed a single char string
that is not null terminated, so there is a potential read overrun
along the stack when parsing for an integer value.  Fix this by
instead using a 2 char string that is initialized to all zeros
to ensure that a 1 char read into the string is always terminated
with a \0.

Detected by cppcheck:
"Invalid atoi() argument nr 1. A nul-terminated string is required."

Fixes: 3391ba0e2792 ("usbip: tools: Extract generic code to be shared with vudc backend")
Signed-off-by: Colin Ian King 
Signed-off-by: Greg Kroah-Hartman 
Signed-off-by: Sasha Levin

usbip: tools: Fix read_usb_vudc_device() error path handling

2019-11-12T18:21:09+00:00

[ Upstream commit 28df0642abbf6d66908a2858922a7e4b21cdd8c2 ]

This isn't really accurate right. fread() doesn't always
return 0 in error. It could return < number of elements
and set errno.

Signed-off-by: GwanYeong Kim 
Acked-by: Shuah Khan 
Link: https://lore.kernel.org/r/20191018032223.4644-1-gy741.kim@gmail.com
Signed-off-by: Greg Kroah-Hartman 
Signed-off-by: Sasha Levin

usbip: fix vhci_hcd controller counting

2019-04-20T07:16:01+00:00

[ Upstream commit e0a2e73e501c77037c8756137e87b12c7c3c9793 ]

Without this usbip fails on a machine with devices
that lexicographically come after vhci_hcd.

ie.
  $ ls -l /sys/devices/platform
  ...
  drwxr-xr-x. 4 root root    0 Sep 19 16:21 serial8250
  -rw-r--r--. 1 root root 4096 Sep 19 23:50 uevent
  drwxr-xr-x. 6 root root    0 Sep 20 13:15 vhci_hcd.0
  drwxr-xr-x. 4 root root    0 Sep 19 16:22 w83627hf.656

Because it detects 'w83627hf.656' as another vhci_hcd controller,
and then fails to be able to talk to it.

Note: this doesn't actually fix usbip's support for multiple
controllers... that's still broken for other reasons
("vhci_hcd.0" is hardcoded in a string macro), but is enough to
actually make it work on the above machine.

See also:
  https://bugzilla.redhat.com/show_bug.cgi?id=1631148

Cc: Jonathan Dieter 
Cc: Valentina Manea 
Cc: Shuah Khan 
Cc: linux-usb@vger.kernel.org
Signed-off-by: Maciej Żenczykowski 
Acked-by: Shuah Khan (Samsung OSG) 
Tested-by: Jonathan Dieter 
Signed-off-by: Greg Kroah-Hartman 
Signed-off-by: Sasha Levin

usbip: dynamically allocate idev by nports found in sysfs

2018-05-31T10:43:14+00:00

As the amount of available ports varies by the kernels build
configuration. To remove the limitation of the fixed 128 ports
we allocate the amount of idevs by using the number we get
from the kernel.

Signed-off-by: Michael Grzeschik 
Acked-by: Shuah Khan (Samsung OSG) 
Signed-off-by: Greg Kroah-Hartman

usbip: usbip_host_common: Use new error codes to return request status

2018-03-09T17:17:08+00:00

Currently ST_OK and ST_NA are the only values used to communicate
status of a request from a client. Use new error codes to clearly
indicate what failed. For example, when client sends request to
import a device that isn't export-able, send ST_DEV_BUSY to the client.

Signed-off-by: Shuah Khan 
Signed-off-by: Greg Kroah-Hartman

usbip: tools: add more error codes for usbip request/reply messages

2018-03-09T17:17:08+00:00

Currently ST_OK and ST_NA are the only values defined to communicate
status of a request from a client. Add more error codes to clearly
indicate what failed. For example, when client sends request to import
a device that isn't export-able, server can send a specific error code
to the client.

Existing defines are moved to a common header in libsrc to be included
in the libusbip_la-usbip_common.o to be used by all the usbip tools.
Supporting interface to print error strings is added to the common lib.

Signed-off-by: Shuah Khan 
Signed-off-by: Greg Kroah-Hartman

tools: usb: usbip: fix fd leak in case of 'fread' failure

2018-01-04T16:05:55+00:00

Fix possible resource leak: fd

Signed-off-by: Elad Wexler 
Acked-by: Shuah Khan 
Signed-off-by: Greg Kroah-Hartman

tools: usb: usbip_device_driver: prefer 'unsigned int' to 'unsigned'

2018-01-04T16:05:55+00:00

Fixup a coding style issue

Signed-off-by: Elad Wexler 
Acked-by: Shuah Khan 
Signed-off-by: Greg Kroah-Hartman