Bug 598862 - spice-usb-redirector needs to cleanup nicely its named semaphore
spice-usb-redirector needs to cleanup nicely its named semaphore
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: spice-usb-redirector (Show other bugs)
All Linux
low Severity medium
: rc
: ---
Assigned To: Gal Hammer
Desktop QE
Depends On:
  Show dependency treegraph
Reported: 2010-06-02 04:44 EDT by Uri Lublin
Modified: 2011-06-15 10:43 EDT (History)
4 users (show)

See Also:
Fixed In Version: spice-usb-share-4.5-3.el5
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-01-13 18:47:19 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
usbrdr: unlink semaphore file name on close. (1.48 KB, patch)
2010-09-15 10:52 EDT, Uri Lublin
no flags Details | Diff

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0122 normal SHIPPED_LIVE spice-usb-share and kspiceusb-kmod bug fix update (was spice-usb-redirector) 2011-01-12 12:28:42 EST

  None (edit)
Description Uri Lublin 2010-06-02 04:44:43 EDT
Description of problem:
spice-usb-redirector uses a named semaphore to get events from the usb-redirector daemon. It creates the semaphore with sem_open but never calls sem_unlink as it should.

Version-Release number of selected component (if applicable):

Additional info:
The leftovers can be seen with 'ls /dev/shm/sem.usbrdr*'
Comment 3 Uri Lublin 2010-09-15 10:52:26 EDT
Created attachment 447494 [details]
usbrdr: unlink semaphore file name on close.
Comment 6 Lubos Kocman 2010-11-02 12:42:33 EDT
Verified on spice-usb-share-4.5-3.el5

unlink is present in the code. spice-usb-share works.
Comment 8 errata-xmlrpc 2011-01-13 18:47:19 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.