[Bug 1053757] New: multipathd daemon: Fix incorrect use of CLOCK_MONOTONIC in pthread
http://bugzilla.suse.com/show_bug.cgi?id=1053757 Bug ID: 1053757 Summary: multipathd daemon: Fix incorrect use of CLOCK_MONOTONIC in pthread Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: martin.wilck@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 736552 --> http://bugzilla.suse.com/attachment.cgi?id=736552&action=edit Patch from dm-devel Issue: When multipathd is starting up, it will reply "timeout\n" immediatly when got any IPC command from socket. The expected way is to wait uxsock_timeout/1000 seconds. Root cause: pthread_mutex_timedlock() is expecting a CLOCK_REALTIME time. Fix: Use CLOCK_REALTIME for pthread_mutex_timedlock(). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1053757
Chenzi Cao
http://bugzilla.suse.com/show_bug.cgi?id=1053757
Hannes Reinecke
http://bugzilla.suse.com/show_bug.cgi?id=1053757
http://bugzilla.suse.com/show_bug.cgi?id=1053757#c1
Martin Wilck
participants (1)
-
bugzilla_noreply@novell.com