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.
Fixing data race condition in buffered.go
Motivation:
I discovered this race condition after running a stress test with
race
flag against the Facebook RSocket Server/Client:It is possible for two separate
goroutines
to race on theinner
field which can result in the following issues:nil
value of buffer being placed backed into the global pool (which later could result in anil
dereference panic).Modifications:
To fix the issue - I made the
inner
field (the buffer) always accessed via atomic operations (atomic Store/Load/CompareAndSwap) to ensure that reads/writes to theinner
field are atomic.Result:
With this fix - the data race goes away.