-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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-38738: [C++] Check variadic buffer counts in bounds #38740
GH-38738: [C++] Check variadic buffer counts in bounds #38740
Conversation
Should the fuzzer testcases be added to testing/data/arrow-ipc-stream/ ? |
Yes, they should |
Co-authored-by: Antoine Pitrou <[email protected]>
fuzz regression file added in apache/arrow-testing#98 |
After merging your PR, Conbench analyzed the 5 benchmarking runs that have been run so far on merge-commit 84c15da. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 6 possible false positives for unstable benchmarks that are known to sometimes produce them. |
…38740) ### Rationale for this change Invalid variadic buffer counts can cause allocating storage for variadic buffers to fail. ### What changes are included in this PR? Check variadic buffer counts are valid before they are used as an allocator argument. ### Are these changes tested? They pass with the fuzzer testcase. ### Are there any user-facing changes? No * Closes: apache#38738 Lead-authored-by: Benjamin Kietzman <[email protected]> Co-authored-by: Antoine Pitrou <[email protected]> Signed-off-by: Benjamin Kietzman <[email protected]>
Rationale for this change
Invalid variadic buffer counts can cause allocating storage for variadic buffers to fail.
What changes are included in this PR?
Check variadic buffer counts are valid before they are used as an allocator argument.
Are these changes tested?
They pass with the fuzzer testcase.
Are there any user-facing changes?
No