Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
接近 2 年 前同步成功

通知 170
Star 36
Fork 7
cloud-kernel
cloud-kernel
切换分支/标签
  1. 19 4月, 2016 1 次提交
    • N
      usbip: event handler as one thread · bb7871ad
      由 Nobuo Iwata 提交于 
      Dear all,

1. Overview

In current USB/IP implementation, event kernel threads are created for
each port. The functions of the threads are closing connection and
error handling so they don't have not so many events to handle. There's
no need to have thread for each port.

BEFORE) vhci side - VHCI_NPORTS(8) threads are created.
$ ps aux | grep usbip
root     10059  0.0  0.0      0     0 ?        S    17:06   0:00 [usbip_eh]
root     10060  0.0  0.0      0     0 ?        S    17:06   0:00 [usbip_eh]
root     10061  0.0  0.0      0     0 ?        S    17:06   0:00 [usbip_eh]
root     10062  0.0  0.0      0     0 ?        S    17:06   0:00 [usbip_eh]
root     10063  0.0  0.0      0     0 ?        S    17:06   0:00 [usbip_eh]
root     10064  0.0  0.0      0     0 ?        S    17:06   0:00 [usbip_eh]
root     10065  0.0  0.0      0     0 ?        S    17:06   0:00 [usbip_eh]
root     10066  0.0  0.0      0     0 ?        S    17:06   0:00 [usbip_eh]

BEFORE) stub side - threads will be created every bind operation.
$ ps aux | grep usbip
root      8368  0.0  0.0      0     0 ?        S    17:56   0:00 [usbip_eh]
root      8399  0.0  0.0      0     0 ?        S    17:56   0:00 [usbip_eh]

This patch put event threads of stub and vhci driver as one workqueue.

AFTER) only one event threads in each vhci and stub side.
$ ps aux | grep usbip
root     10457  0.0  0.0      0     0 ?        S<   17:47   0:00 [usbip_event]

2. Modification to usbip_event.c

BEFORE) kernel threads are created in usbip_start_eh().

AFTER) one workqueue is created in new usbip_init_eh().

Event handler which was main loop of kernel thread is modified to
workqueue handler.

Events themselves are stored in struct usbip_device - same as before.
usbip_devices which have event are listed in event_list.

The handler picks an element from the list and wakeup usbip_device. The
wakeup method is same as before.

usbip_in_eh() substitutes statement which checks whether functions are
called from eh_ops or not. In this function, the worker context is used
for the checking. The context will be set in a variable in the
beginning of first event handling. usbip_in_eh() is used in event
handler so it works well.

3. Modifications to programs using usbip_event.c

Initialization and termination of workqueue are added to init and exit
routine of usbip_core respectively.

A. version info

v2)
# Merged 1/2 event handler itself and 2/2 user programs because of auto
build fail at 1/2 casued unmodified user programs in 1/2.
Signed-off-by: NNobuo Iwata <nobuo.iwata@fujixerox.co.jp>
Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      bb7871ad
  3. 31 3月, 2016 1 次提交
    • I
      USB: usbip: fix potential out-of-bounds write · b348d7dd
      由 Ignat Korchagin 提交于 
      Fix potential out-of-bounds write to urb->transfer_buffer
usbip handles network communication directly in the kernel. When receiving a
packet from its peer, usbip code parses headers according to protocol. As
part of this parsing urb->actual_length is filled. Since the input for
urb->actual_length comes from the network, it should be treated as untrusted.
Any entity controlling the network may put any value in the input and the
preallocated urb->transfer_buffer may not be large enough to hold the data.
Thus, the malicious entity is able to write arbitrary data to kernel memory.
Signed-off-by: NIgnat Korchagin <ignat.korchagin@gmail.com>
Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      b348d7dd
  5. 26 8月, 2014 1 次提交
  7. 02 4月, 2014 1 次提交
  9. 20 3月, 2014 1 次提交
  11. 07 3月, 2014 1 次提交
  13. 08 2月, 2014 1 次提交
  15. 16 12月, 2013 1 次提交
  17. 11 11月, 2013 1 次提交
  19. 27 8月, 2013 1 次提交
  21. 06 4月, 2013 1 次提交
  23. 23 2月, 2013 1 次提交
  25. 18 1月, 2013 1 次提交
  27. 23 10月, 2012 3 次提交
  29. 11 9月, 2012 1 次提交
  31. 18 8月, 2012 1 次提交
  33. 15 5月, 2012 1 次提交
  35. 12 5月, 2012 1 次提交
  37. 10 2月, 2012 1 次提交
  39. 23 12月, 2011 1 次提交
  41. 01 11月, 2011 1 次提交
  43. 08 6月, 2011 4 次提交
  45. 20 5月, 2011 1 次提交
  47. 18 5月, 2011 1 次提交
  49. 13 5月, 2011 2 次提交
  51. 12 5月, 2011 2 次提交
  53. 07 5月, 2011 4 次提交
  55. 07 4月, 2011 2 次提交
  57. 03 3月, 2011 1 次提交
    • A
      staging/usbip: convert to kthread · 9720b4bc
      由 Arnd Bergmann 提交于 
      usbip has its own infrastructure for managing kernel
threads, similar to kthread. By changing it to use
the standard functions, we can simplify the code
and get rid of one of the last BKL users at the
same time.

Includes changes suggested by Max Vozeler.
Signed-off-by: NArnd Bergmann <arnd@arndb.de>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
Cc: Takahiro Hirofuchi <hirofuchi@users.sourceforge.net>
Cc: Max Vozeler <max@vozeler.com>
Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      9720b4bc