Skip to content
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

Fix a potential use-after-free bug #54

Merged
merged 1 commit into from
Nov 29, 2023

Conversation

godlygeek
Copy link
Contributor

It'd be hard to trigger, and would require a race between threads, but this defends against the issue.

It'd be hard to trigger, and would require a race between threads, but
this defends against the issue.

Signed-off-by: Matt Wozniski <[email protected]>
@godlygeek godlygeek self-assigned this Nov 28, 2023
Copy link
Contributor

@sarahmonod sarahmonod left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, I thought simply holding the list was enough 😅 thanks for fixing this though!

@sarahmonod sarahmonod merged commit bd01ee0 into bloomberg:main Nov 29, 2023
@godlygeek
Copy link
Contributor Author

Oh, I thought simply holding the list was enough

It is for everything else, but the list of bytes is the one exception - it's the one place where we'd be holding a reference to a mutable object that the caller also holds a reference to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants