-
Notifications
You must be signed in to change notification settings - Fork 932
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 the GDS read/write segfault/bus error when the cuFile policy is set to GDS or ALWAYS #17122
Fix the GDS read/write segfault/bus error when the cuFile policy is set to GDS or ALWAYS #17122
Conversation
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.
Awesome
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.
Are we backporting this to 24.10? That’s what the title “hotfix” implies. If so, let’s merge this to 24.12 without the word “hotfix” in the title (it goes into the changelog) and we can name the backport PR “hotfix” if needed.
@@ -239,7 +239,7 @@ std::vector<std::future<ResultT>> make_sliced_tasks( | |||
std::vector<std::future<ResultT>> slice_tasks; | |||
std::transform(slices.cbegin(), slices.cend(), std::back_inserter(slice_tasks), [&](auto& slice) { | |||
return pool.submit_task( | |||
[&] { return function(ptr + slice.offset, slice.size, offset + slice.offset); }); | |||
[=] { return function(ptr + slice.offset, slice.size, offset + slice.offset); }); |
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.
I don't understand how this worked for as long as it did.
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.
It is similar to the bug that I recently fixed for ORC reader, when reading file using the default stream 0
. It's never showed up until recently.
/merge |
Description
When
LIBCUDF_CUFILE_POLICY
is set toGDS
orALWAYS
, cuDF uses an internal implementation to call the cuFile API and harness the GDS feature. Recent tests with these two settings were unsuccessful due to program crash. Specifically, for thePARQUET_READER_NVBENCH
'sparquet_read_io_compression
benchmark:The root cause is the use of dangling reference, which occurs when a variable is captured by reference by nested lambdas. This PR performs a hotfix that turns out to be a 1-char change.
Checklist