-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8361085: MemoryReserver log_on_large_pages_failure has incorrect format usage #26050
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
Conversation
👋 Welcome back kbarrett! A progress list of the required criteria for merging this PR into |
@kimbarrett 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 22 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 |
@kimbarrett The following label 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 list. If you would like to change these labels, use the /label pull request command. |
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.
It is strange that this pattern of doing a warning used to be used in a few places, even though warning
has always been able to handle the formatting directly.
Thanks for reviews @stefank and @dholmes-ora |
/integrate |
Going to push as commit 1703915.
Your commit was automatically rebased without conflicts. |
@kimbarrett Pushed as commit 1703915. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Please review this fix of an incorrect format usage.
The function calls
jio_snprintf
to format a message into a buffer. Thatmessage includes printing a pointer using
PTR_FORMAT
, but isn't using thep2i
helper function. Fixing that is just a matter of using that helper.However, there's no need to use
jio_snprintf
here, as the resulting messageis then just passed to
warning
, which can handle output formatting directly.So we also move the formatting to the
warning
call, and remove the use ofjio_snprintf
. Note that callingwarning
without thep2i
would haveproduced a compiler warning about the incorrect format usage.
Testing: mach5 tier1
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/26050/head:pull/26050
$ git checkout pull/26050
Update a local copy of the PR:
$ git checkout pull/26050
$ git pull https://git.openjdk.org/jdk.git pull/26050/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 26050
View PR using the GUI difftool:
$ git pr show -t 26050
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/26050.diff
Using Webrev
Link to Webrev Comment