-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8360942: [ubsan] aotCache tests trigger runtime error: applying non-zero offset 16 to null pointer in CodeBlob::relocation_end() #26175
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
base: master
Are you sure you want to change the base?
Conversation
…ero offset 16 to null pointer in CodeBlob::relocation_end()
👋 Welcome back kvn! A progress list of the required criteria for merging this PR into |
@vnkozlov This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 9 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
@MBaesken, please verify that is passing ubsan testing now. |
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.
Looks good.
Hi Vladimir, I do not see the mentioned ubsan error (codeBlob.hpp:235:97: runtime error: applying non-zero offset 16 to null pointer) after your patch was added! |
CodeBlob::relocation_size()
is calculated as(_mutable_data + _relocation_size - _mutable_data)
.CodeBlob::relocation_size()
is called during AOT code loading before we allocate space for mutable data (the size is used to find how big space should be allocated). The expression at that point is(NULL + _relocation_size - NULL)
which returns correct result. But we should just return_relocation_size
which is recorded anyway in AOT data.Added missing
_mutable_data = blob_end();
initialization when we restore AOT code blob.Fixed embarrassing typo in asserts.
Tested: tier1-6,8,10,xcomp,stress
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/26175/head:pull/26175
$ git checkout pull/26175
Update a local copy of the PR:
$ git checkout pull/26175
$ git pull https://git.openjdk.org/jdk.git pull/26175/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 26175
View PR using the GUI difftool:
$ git pr show -t 26175
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/26175.diff
Using Webrev
Link to Webrev Comment