Skip to content

Conversation

@pfalcon
Copy link
Contributor

@pfalcon pfalcon commented Aug 27, 2019

This fixes 2 POSIX Pthreads functions incorrectly treating their param as a relative timeout, instead of absolute deadline, as spotted by @jimparis in #17812, #17813.

Fixes: #17812

@pfalcon pfalcon added priority: medium Medium impact/importance bug area: POSIX POSIX API Library labels Aug 27, 2019
@pfalcon pfalcon added this to the v2.0.0 milestone Aug 27, 2019
@pfalcon pfalcon requested review from andyross and jimparis August 27, 2019 13:01
@pfalcon pfalcon added the bug The issue is a bug, or the PR is fixing a bug label Aug 27, 2019
@pfalcon pfalcon requested a review from andrewboie August 27, 2019 13:02
@pfalcon
Copy link
Contributor Author

pfalcon commented Aug 27, 2019

This is from-scratch alternative to #17813, containing absolutely minimal set of changes to fix reported issues, to not introduce further issues, like leaking of private functions into public headers, renaming unrelated functions in a way which may conflict with ANSI C/MISRA C (using leading underscore), etc.

@zephyrbot zephyrbot added the area: API Changes to public APIs label Aug 27, 2019
Copy link
Contributor

@jimparis jimparis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested & working. Thanks.

@nashif nashif merged commit 0906671 into zephyrproject-rtos:master Aug 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: API Changes to public APIs area: POSIX POSIX API Library bug The issue is a bug, or the PR is fixing a bug priority: medium Medium impact/importance bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

pthread_cond_timedwait interprets timeout wrong

5 participants