-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
GH-38479: [C++] Avoid passing null pointer to LZ4 frame decompressor #39125
Conversation
|
@github-actions crossbow submit sanitize |
Revision: a4ca020 Submitted crossbow builds: ursacomputing/crossbow @ actions-096f0cf193
|
@kou There seem to be recurring C/GLib CI failures in various PRs: |
@paleolimbot Seems like the R sanitizer build succeeded. |
I've opened a new issue for it: #39130 |
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.
+1
@felipecrv Do you want to merge this as a new committer?
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.
Thank you!
After merging your PR, Conbench analyzed the 6 benchmarking runs that have been run so far on merge-commit b75755a. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 4 possible false positives for unstable benchmarks that are known to sometimes produce them. |
…essor (apache#39125) ### Rationale for this change Avoid undefined behavior in LZ4 when adding an offset to a null pointer. ### Are these changes tested? Yes. ### Are there any user-facing changes? No. * Closes: apache#38479
…essor (apache#39125) ### Rationale for this change Avoid undefined behavior in LZ4 when adding an offset to a null pointer. ### Are these changes tested? Yes. ### Are there any user-facing changes? No. * Closes: apache#38479
…essor (apache#39125) ### Rationale for this change Avoid undefined behavior in LZ4 when adding an offset to a null pointer. ### Are these changes tested? Yes. ### Are there any user-facing changes? No. * Closes: apache#38479
Rationale for this change
Avoid undefined behavior in LZ4 when adding an offset to a null pointer.
Are these changes tested?
Yes.
Are there any user-facing changes?
No.