-
Notifications
You must be signed in to change notification settings - Fork 915
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 branch_stack calculation in row_bit_count()
#9076
Fix branch_stack calculation in row_bit_count()
#9076
Conversation
For input with a number of rows exceeding `max_block_size`, `row_bit_count()` currently reaches past the bounds of its shared-memory allocation, causing illegal memory access errors like in (cudf/issues/8938)[rapidsai#8938]. This commit corrects the calculation of the branch stack's base address, and adds a test for this case.
Good fix. Thanks. |
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.
Just one small note about potentially choosing a row count that will blow any reasonable block size limit.
Codecov Report
@@ Coverage Diff @@
## branch-21.10 #9076 +/- ##
===============================================
Coverage ? 10.73%
===============================================
Files ? 114
Lines ? 19058
Branches ? 0
===============================================
Hits ? 2046
Misses ? 17012
Partials ? 0 Continue to review full report at Codecov.
|
@gpucibot merge |
Thanks for the reviews, chaps. I've merged this change now. |
Fixes #8938.
For input with a number of rows exceeding
max_block_size
,row_bit_count()
currentlyreaches past the bounds of its shared-memory allocation, causing illegal memory access
errors like in cudf/issues/8938.
This commit corrects the calculation of the branch stack's base address, and adds a
test for this case.