| commit | 74f418b29d1e9463028f2ae4cc2a9c74d39aeaab | |
| author | Adhemerval Zanella <adhemerval.zanella@linaro.org> | |
| Thu, 29 Oct 2020 18:34:31 +0000 (29 15:34 -0300) | ||
| committer | Adhemerval Zanella <adhemerval.zanella@linaro.org> | |
| Wed, 25 Nov 2020 13:46:22 +0000 (25 10:46 -0300) | ||
| tree | afc76155ba0a5384bc6d142742441dc2b27cdc6a | treesnapshot (tar.gz zip) |
| parent | b45b1c5ba1df4d0315ffdd00a040ff9bc0597a8d | commitdiff |
nptl: Return EINVAL for pthread_mutex_clocklock/PI with CLOCK_MONOTONIC [BZ #26801]
Linux futex FUTEX_LOCK_PI operation only supports CLOCK_REALTIME,
so pthread_mutex_clocklock operation with priority aware mutexes
may fail depending of the input timeout.
Also, it is not possible to convert a CLOCK_MONOTONIC to a
CLOCK_REALTIME due the possible wall clock time change which might
invalid the requested timeout.
Checked on x86_64-linux-gnu and i686-linux-gnu.
Reviewed-by: Lukasz Majewski <lukma@denx.de>
Linux futex FUTEX_LOCK_PI operation only supports CLOCK_REALTIME,
so pthread_mutex_clocklock operation with priority aware mutexes
may fail depending of the input timeout.
Also, it is not possible to convert a CLOCK_MONOTONIC to a
CLOCK_REALTIME due the possible wall clock time change which might
invalid the requested timeout.
Checked on x86_64-linux-gnu and i686-linux-gnu.
Reviewed-by: Lukasz Majewski <lukma@denx.de>