Skip to content

Fix OSS-Fuzz #427814456 #18951

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

Closed
wants to merge 1 commit into from
Closed

Conversation

nielsdos
Copy link
Member

The first warning may trigger an error handler, destroying the operand and its string. So we need to protect the string in that case. Care was taken to avoid unnecessary refcounts and to avoid touching the hot code path.

@nielsdos nielsdos marked this pull request as ready for review June 27, 2025 06:46
@nielsdos nielsdos requested a review from iluuu1994 June 27, 2025 21:22
The first warning may trigger an error handler, destroying the operand
and its string. So we need to protect the string in that case.
Care was taken to avoid unnecessary refcounts and to avoid touching the
hot code path.
@nielsdos nielsdos force-pushed the fix-oss-fuzz-427814456 branch from 75d8067 to 313b82e Compare June 28, 2025 12:44
Copy link
Member

@iluuu1994 iluuu1994 left a comment

Choose a reason for hiding this comment

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

Looks reasonable 👍

@iluuu1994
Copy link
Member

iluuu1994 commented Jul 1, 2025

Ps. Do we backport these? I usually target master.

@nielsdos
Copy link
Member Author

nielsdos commented Jul 1, 2025

Ps. Do we backport these? I usually target master.

Uh dunno. This is not particularly important, but it doesn't harm merging this in a lower branch as the fix is very local. I suppose one potential advantange is reducing the risk of merge conflicts.

@nielsdos nielsdos closed this in 9174984 Jul 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants