Opened on 05/18/21 at 11:09:45

Closed on 05/18/21 at 18:32:39

Last modified on 06/23/21 at 07:07:55

#4426 closed defect (fixed)

clock_nanosleep() may use wrong clock for relative times

Reported by: Sebastian Huber Owned by: Sebastian Huber
Priority: normal Milestone: 6.1
Component: posix Version: 6
Severity: normal Keywords: qualification
Cc: Blocked By:
Blocking:

Description (last modified by Sebastian Huber)

For relative times, the clock identifier is not used to select the clock and instead always the CLOCK_MONOTONIC is used. A side-effect is that sleep() and nanosleep() use the wrong clock (CLOCK_MONOTONIC instead of CLOCK_REALTIME).

Change History (3)

comment:1 Changed on 05/18/21 at 11:55:05 by Sebastian Huber

Description: modified (diff)

comment:2 Changed on 05/18/21 at 18:32:39 by Sebastian Huber <sebastian.huber@…>

Resolution: → fixed
Status: assigned → closed

In 24c62932/rtems:

posix: Fix use of clock for relative times

Close #4426.

comment:3 Changed on 06/23/21 at 07:07:55 by Sebastian Huber

Keywords: qualification added
Note: See TracTickets for help on using tickets.