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.
rls: fix child lb leak when client channel is shutdown #8750
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
rls: fix child lb leak when client channel is shutdown #8750
Changes from all commits
1268355
2e48bb0
c72762d
443bd73
303d95b
3ae4e3d
7d356e0
5aa5cd2
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Do we care if this operation competes before returning a ChildPolicyWrapper object?
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.
Good catch! There's a (pre-existing) concurrency issue with
RefCountedChildPolicyWrapperFactory.createOrGet()
andrelease()
. As long as they become thread-safe, it doesn't matter whenshutdown()
operation completes.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.
Fixed the concurrency issue in 3ae4e3d
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.
Is this possible that in concurrent environment one thread sets
childPolicyWrapper = null
, and another will callchildPolicyWrapper.shutdown()
causing NPE?I'm not sure if
AtomicLong
volatility visibility guarantee is sufficient. IRRC becausechildPolicyWrapper = null
comes after the write to the volatile variable, it's not guaranteed to flush immediately.Should
returnObject()
be fully synchronized?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.
Fixed the concurrency issue in 3ae4e3d