Skip to content

Conversation

@DamonGuy
Copy link
Contributor

@DamonGuy DamonGuy commented Dec 22, 2025

This update is to fix the potential issue where tmpbuf can be read as a format argument for fprintf. I have added a specifier here to avoid this issue since the string from tmpbuf is not guaranteed to not cause issues. This update should make this print more reliable and safe to use.


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8373475: Unintentional format string in logString of AccessInfo.cpp (Bug - P3)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 28950

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/28950.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Dec 22, 2025

👋 Welcome back dnguyen! 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
Copy link

openjdk bot commented Dec 22, 2025

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

8373475: Unintentional format string in logString of AccessInfo.cpp

Reviewed-by: aivanov, prr, azvegint

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 131 new commits pushed to 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.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

@openjdk
Copy link

openjdk bot commented Dec 22, 2025

@DamonGuy The following label will be automatically applied to this pull request:

  • client

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.

@openjdk openjdk bot added the rfr Pull request is ready for review label Dec 22, 2025
@mlbridge
Copy link

mlbridge bot commented Dec 22, 2025

Webrevs

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Dec 22, 2025

fprintf(logfile, tmpbuf);
fprintf(logfile, "\n");
fprintf(logfile, "%s\n", tmpbuf);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why can't we use fputs and avoid all the format string logic and ambiguity altogether?

Alternatively, use vfprintf directly instead of first formatting the arguments into a temporary buffer with vsnprintf and then sending the result to the output.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A similar pattern is used elsewhere in this file. And I don't want this fix to become a reworking of this code, because that isn't a goal here.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After reading about fputs, I think this is best. Like you mentioned, no ambiguity since it does not use specifiers. Updated.

Copy link
Member

@aivanov-jdk aivanov-jdk Dec 23, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A similar pattern is used elsewhere in this file. And I don't want this fix to become a reworking of this code, because that isn't a goal here.

Indeed, it is.

I agree it's better to keep the code consistent.

At the same time, I think it's worth submitting a bug to simplify usages like that, fputs works perfectly for strings that don't require formatting.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since Damon already made the change and its just one line I'm fine to keep it but not go looking for more.


fprintf(logfile, tmpbuf);
fprintf(logfile, "\n");
fprintf(logfile, "%s\n", tmpbuf);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A similar pattern is used elsewhere in this file. And I don't want this fix to become a reworking of this code, because that isn't a goal here.

@openjdk openjdk bot removed the ready Pull request is ready to be integrated label Dec 23, 2025
Copy link
Contributor

@prrace prrace left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wait where's the \n gone ?

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Dec 23, 2025

fprintf(logfile, tmpbuf);
fprintf(logfile, "\n");
fputs(tmpbuf, logfile);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since fputs doesn't add a line break automatically, you have to add it explicitly.

    fputs(tmpbuf, logfile);
    fputs("\n", logfile);

Copy link
Contributor Author

@DamonGuy DamonGuy Dec 23, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for catching this too!

@openjdk openjdk bot removed the ready Pull request is ready to be integrated label Dec 23, 2025

fprintf(logfile, tmpbuf);
fprintf(logfile, "\n");
fputs(tmpbuf, logfile);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

unless I'm missing something you'd need to add a 2nd fputs for the newline or go back to fprintf like before the latest comment.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have gone back to fprintf for consistency as you mentioned above. Newline is included. Thanks!

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Dec 23, 2025
@DamonGuy
Copy link
Contributor Author

/integrate

@openjdk
Copy link

openjdk bot commented Dec 24, 2025

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

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Dec 24, 2025
@openjdk openjdk bot closed this Dec 24, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Dec 24, 2025
@openjdk
Copy link

openjdk bot commented Dec 24, 2025

@DamonGuy Pushed as commit a59dbc5.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

client [email protected] integrated Pull request has been integrated

Development

Successfully merging this pull request may close these issues.

4 participants