-
Notifications
You must be signed in to change notification settings - Fork 506
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
Crash in rayon_core::latch::TickleLatch::set
#768
Comments
Looking at rayon code it looks like there might be a data race that could cause this crash.
and then returns. Meanwhile
Is it possible that |
Needless to say this crash is highly intermittent and we have no way to reliably reproduce it. |
Assuming this analysis is correct, I guess one way to fix it would be to change |
I think it probably would be a good idea to ship a fix given that the UAF has been known for over two months now. |
If there are other known unfixed UAF/safety bugs then it would be helpful if you list them somewhere for future reference. |
I guess we could use an "unsound" label or something, but really we just shouldn't have let this fix linger at all. I'll merge that PR and prepare a point release. I'm not aware of any other such bugs. There are deadlock hazards like #592, but that's a different category of problem. |
I've released the fix in rayon-core 1.7.1, and rayon 1.3.1 also bumped its requirement.
Kudos for coming to the same analysis and fix as I had -- that's nice validation! |
We're getting a
SIGSEGV
in rayon under load with cross-ThreadPool
dispatch.The faulting RIP is
11cd2c0
here:The fault address (RDI) is zero.
The text was updated successfully, but these errors were encountered: