Fix race condition in kqueue event system implementation #2193
Conversation
This file contains 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
SeanTAllen
force-pushed
the
signal_hunt
branch
3 times, most recently
from
dd326a6
to
77c6df3
Compare
SeanTAllen
force-pushed
the
signal_hunt
branch
from
77c6df3
to
b547c9b
Compare
SeanTAllen
added
the
changelog - fixed
sylvanc
approved these changes
Aug 26, 2017
SeanTAllen
changed the title
ponylang-main
added a commit
that referenced
this pull request
Aug 26, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This fixes a race condition in the
kqueueback-end. Previously, it was possible for an unsubscribed (i.e.ASIO_DISPOSABLE) to be sent as an event in between being disposed and being sent as anASIO_DISPOSABLEevent. This could cause an event that had been unsubscribed to receive a read or a write event immediately before a dispose event.