1. 05 1月, 2018 1 次提交
  2. 19 12月, 2017 1 次提交
  3. 07 11月, 2017 1 次提交
    • G
      USB: usbip: Remove redundant license text · 7f2b019c
      Greg Kroah-Hartman 提交于
      Now that the SPDX tag is in all USB files, that identifies the license
      in a specific and legally-defined manner.  So the extra GPL text wording
      can be removed as it is no longer needed at all.
      
      This is done on a quest to remove the 700+ different ways that files in
      the kernel describe the GPL license text.  And there's unneeded stuff
      like the address (sometimes incorrect) for the FSF which is never
      needed.
      
      No copyright headers or other non-license-description text was removed.
      
      Cc: Valentina Manea <valentina.manea.m@gmail.com>
      Acked-by: NShuah Khan <shuahkh@osg.samsung.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      7f2b019c
  4. 04 11月, 2017 1 次提交
  5. 22 7月, 2017 1 次提交
  6. 28 2月, 2017 1 次提交
  7. 27 12月, 2016 1 次提交
  8. 27 4月, 2016 1 次提交
  9. 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
  10. 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
  11. 26 8月, 2014 1 次提交
  12. 02 4月, 2014 1 次提交
  13. 20 3月, 2014 1 次提交
  14. 07 3月, 2014 1 次提交
  15. 08 2月, 2014 1 次提交
  16. 16 12月, 2013 1 次提交
  17. 11 11月, 2013 1 次提交
  18. 27 8月, 2013 1 次提交
  19. 06 4月, 2013 1 次提交
  20. 23 2月, 2013 1 次提交
  21. 18 1月, 2013 1 次提交
  22. 23 10月, 2012 3 次提交
  23. 11 9月, 2012 1 次提交
  24. 18 8月, 2012 1 次提交
  25. 15 5月, 2012 1 次提交
  26. 12 5月, 2012 1 次提交
  27. 10 2月, 2012 1 次提交
  28. 23 12月, 2011 1 次提交
  29. 01 11月, 2011 1 次提交
  30. 08 6月, 2011 4 次提交
  31. 20 5月, 2011 1 次提交
  32. 18 5月, 2011 1 次提交
  33. 13 5月, 2011 2 次提交
  34. 12 5月, 2011 1 次提交