8333887: ubsan: unsafe.cpp:247:13: runtime error: store to null pointer of type 'volatile int'

[luwang1103]

hi ，

This pull request contains a backport of commit 0d3a3771 from the master repository.

The commit being backported was authored by Matthias Baesken on 13 Jun 2024.

Thanks！

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• JDK-8333887 needs maintainer approval

Issue

• JDK-8333887: ubsan: unsafe.cpp:247:13: runtime error: store to null pointer of type 'volatile int' (Bug - P4 - Approved)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk23u.git pull/22/head:pull/22
$ git checkout pull/22

Update a local copy of the PR:
$ git checkout pull/22
$ git pull https://git.openjdk.org/jdk23u.git pull/22/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 22

View PR using the GUI difftool:
$ git pr show -t 22

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk23u/pull/22.diff

Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back luwang1103! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@luwang1103 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:

8333887: ubsan: unsafe.cpp:247:13: runtime error: store to null pointer of type 'volatile int'

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 1 new commit pushed to the master branch:

• e4d80b1: 8334123: log the opening of Type 1 fonts

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
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.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[openjdk]

This backport pull request has now been updated with issue from the original commit.

[openjdk]

⚠️ @luwang1103 This change is now ready for you to apply for maintainer approval. This can be done directly in each associated issue or by using the /approval command.

[mlbridge]

Webrevs

• 00: Full (bd954c10)

[luwang1103]

/approval request The code applies cleanly. Low risk: It is a corner case which is not triggered by the current code. In order to avoid bugs in the future, it is good to backport it.

[openjdk]

@luwang1103
8333887: The approval request has been created successfully.

[luwang1103]

/integrate

[openjdk]

@luwang1103
Your change (at version bd954c1) is now ready to be sponsored by a Committer.

[luwang1103]

@RealCLanger Can you please sponsor the changes? thanks

[shipilev]

I'll sponsor, as I think this is safe. Going forward, please enable GHA and pass them, see the "Pre-submit test status" in the box above.

[shipilev]

/sponsor

[openjdk]

Going to push as commit 821a3aa.
Since your change was applied there have been 2 commits pushed to the master branch:

• 8883b15: 8325525: Create jtreg test case for JDK-8325203
• e4d80b1: 8334123: log the opening of Type 1 fonts

Your commit was automatically rebased without conflicts.

[openjdk]

@shipilev @luwang1103 Pushed as commit 821a3aa.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.