Repository navigation
Set FUTEX_WAITERS under the bucket lock in LOCK_PI #434
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
+270
−39
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
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
Oops, something went wrong.
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.
The timeout exit still breaks this invariant: it unlinks the waiter, drops
b->lock, and only then callsfutex_clear_waiters_bit. A second waiter that takes the lock in that gap seesFUTEX_WAITERSalready set, takes thefutex_pi_has_waitersbreak and parks. The bit is then cleared under it, and the owner's next release is a guest-side CAS that makes no syscall, which is the same lost wake this change fixes. Moving thefutex_clear_waiters_bit(word)call abovepthread_mutex_unlock(&b->lock)in that branch is safe for the same reason the marking loop is safe under the lock, and it would make this comment true. Otherwise, qualify the comment and keep it on the follow-up list the description already carries.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.
Moved
futex_clear_waiters_bit(word)abovepthread_mutex_unlock(&b->lock)in 097546b, so the check for other waiters and the clear happen under one hold of the bucket lock, and the comment holds as written. There is no test for this path: a stress case that raced an expiredFUTEX_LOCK_PIagainst a parking one passed 16 of 16 runs with only this change reverted, because the gap between the unlock and the clear is a few instructions.