-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
8293197: Avoid double racy reads from non-volatile fields in SharedSecrets #10076
8293197: Avoid double racy reads from non-volatile fields in SharedSecrets #10076
Conversation
👋 Welcome back aturbanov! A progress list of the required criteria for merging this PR into |
@turbanoff The following labels will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command. |
Mailing list message from Bernd Eckenfels on core-libs-dev: BTW, after then ensures it looks like a good candidate for a system-assert for not-null for all of those fields, right? Gruss After integration of [JDK-8259021](https://bugs.openjdk.org/browse/JDK-8259021) a few more fields were added to `SharedSecrets` class. It make sense to update their reading code to use the same idiom. ------------- Commit messages: Changes: https://git.openjdk.org/jdk/pull/10076/files PR: https://git.openjdk.org/jdk/pull/10076 |
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.
Surprising that the additions since JDK-8259021 didn't follow the same pattern but I think some of these were in other repos at the time.
@turbanoff 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 74 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 |
/integrate |
Going to push as commit 2259e42.
Your commit was automatically rebased without conflicts. |
@turbanoff Pushed as commit 2259e42. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
After integration of JDK-8259021 a few more fields were added to
SharedSecrets
class. It make sense to update their reading code to use the same idiom.Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/10076/head:pull/10076
$ git checkout pull/10076
Update a local copy of the PR:
$ git checkout pull/10076
$ git pull https://git.openjdk.org/jdk pull/10076/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 10076
View PR using the GUI difftool:
$ git pr show -t 10076
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/10076.diff