-
Notifications
You must be signed in to change notification settings - Fork 2.1k
xtimer/xtimer.c: xtimer_mutex_lock_timeout fix with short timeout #13199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
MichelRottleuthner
merged 4 commits into
RIOT-OS:master
from
JulianHolzwarth:pr/xtimer_mutex_lock_timeout/short_time_fix
Mar 6, 2020
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
dfeaea3
sys/xtimer/xtimer.c: comment change
JulianHolzwarth 110c725
tests/xtimer_mutex_lock_timeout: minimal xtimer_mutex_lock_timeout test
JulianHolzwarth bce45fd
xtimer/xtimer.c: xtimer_mutex_lock_timeout fix test
JulianHolzwarth 4d85fa1
xtimer/xtimer.c: _mutex_remove_thread_from_waiting_queue
JulianHolzwarth File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
handing the value of the volatile variable
blockingto_mutex_lockwill not have the desired effect here. The timeout might deschedule you right before theirq_disableof_mutex_lockis called, leaving you with a blocking call where actually a non-blocking lock should happen. Is there any reason for not just simply doing a non-blocking lock before setting up the timeout timer? This way you would always try to lock the mutex and if the timeout then happens between setting up the timer and locking it, is actually desired behavior to not lock it, right?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the timeout could happen before the mutex_lock but after the first non blocking mutex lock. Meaning there would be the same problem.
The problem with the irq_disable (interupt in function _mutex_lock but before irq_disable) will be fixed in the next PR. Tracking PR #11660
This PR fixes the problems with smaller timeouts.