core: fix thread_interceptor owner check#574
Merged
sanderpick merged 1 commit intomasterfrom Feb 25, 2022
Merged
Conversation
Signed-off-by: Sander Pick <sanderpick@gmail.com>
sanderpick
force-pushed
the
sander/fix-thread-owner-check
branch
from
df5eeec to
686920c
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 thread id that was being checked for caller ownership is from the context, but
go-threadsmethods take the id as a param. This was being extracted in some cases, but not for the primary owner check.