Description of problem:

  See upstream issue:
    https://github.com/daynix/UsbDk/issues/29

  The commit log of the fix (commit bf79d6e9425b1587aaa542c3)

  On unplug of USB hub that contains a redirected
  device, removal of redirection is started when redirected
  device PDO is still present in UsbDk device lists.
    
  In this case UsbDk will try to send reset IOCTL to this device
  and system will return STATUS_NO_SUCH_DEVICE error code.

  This commit changes behavior of redirection removal
  logic in a way that it will not interrupt removal
  process when such an error is returned by reset.

Upstream issue:
  https://github.com/daynix/UsbDk/issues/29


Version-Release number of selected component (if applicable):
  spice-usbdk-0.1-14

How reproducible:
Consistently, I guess, when a USB hub is unplugged

Steps to Reproduce:
  from upstream issue (report is for specific devices):
    https://github.com/daynix/UsbDk/issues/29#issuecomment-242362095

1. connect USBHUB(VID_05E3&PID_0608) & USBMemory(VID_04BB&PID_0CCB)
2. redirect USBMemory
3. disconnect USBHUB(with USBMemory)
4. press return key (exit UsbDkController.exe)
5. connect USBHUB(VID_05E3&PID_0608) & USBMemory(VID_04BB&PID_0CCB)
6. redirect USBMemory
7. redirect of USB device failed

Actual results:
USB device fails to redirect on 7
(UsbDk does not clean up the device on 3)

Expected results:
USB device can be redirected on 7
(UsbDk cleans up everything on 3)


Additional info:
    Fixed by commit bf79d6e9425b1587aaa542c3