-
Notifications
You must be signed in to change notification settings - Fork 386
Fix: Prevent crash on OOM in error copy #1183
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
Open
schreter
wants to merge
2
commits into
dtolnay:master
Choose a base branch
from
schreter:fix_oom_crash_on_msg_copy
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 am on board with handling OOM in this function without crashing the process. However I think the implementation given in this PR is not correct.
This change makes
errorCopy
return nullptr if it fails to allocate memory to copy the error message. That meanscxxbridge1$error
will return nullptr to Rust.cxx/src/cxx.cc
Lines 458 to 460 in 03b0c8d
That means this Rust code will be holding a
NonNull<u8>
which is actually null, which is immediate language-level UB.cxx/src/result.rs
Lines 45 to 50 in 03b0c8d
Since this is UB we cannot say what really happens, but naively it's likely the null ptr ends up as the
err
field ofunion Result
, which makes the union look like it contains anok
noterr
.cxx/src/result.rs
Lines 51 to 52 in 03b0c8d
cxx/src/result.rs
Lines 13 to 24 in 03b0c8d
C++ will use the nullness of that pointer to determine whether an error has occurred in the Rust function, so it will appear that it has not.
cxx/gen/src/write.rs
Lines 1126 to 1128 in 03b0c8d
The C++ side will continue as if a successful result has been written into the function's output location, which it has not. In reality the output location will be uninitialized. C++ will move or copy out of it which will be UB, and anything the caller does with it will be further UB, including heap corruption or other such issues depending on what data structure the return type is.