Fix mostly-theoretical data race when popping from SPSC queues #149
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
The reader loses access to the front pointer as soon as it pops from the queue, since from that point onward, the writer can overwrite it with a new message. Instead the reader must finish using the pointer or copy the value out, before popping from the queue. This bug terrifies me.
nyanpasu64
force-pushed
the
fix-spsc-data-race
branch
from
b2e2753 to
0e8c5b9
Compare
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.
The reader loses access to the front pointer as soon as it pops from the queue, since from that point onward, the writer can overwrite it with a new message. Instead the reader must finish using the pointer or copy the value out, before popping from the queue.
This bug terrifies me, that I managed to write it, not catch it reviewing my own code despite years of atomic threading experience, and only realized I made a mistake weeks later, when reading an paper (https://lmax-exchange.github.io/disruptor/files/Disruptor-1.0.pdf).