8357682 : sun.security.provider.certpath.Builder#getMatchingPolicies always returns null

[koushikthirupattur]

The method sun.security.provider.certpath.Builder#getMatchingPolicies appears to have been intended as a lazy initialization of the matchingPolicies field of the Builder class. However it checks for "matchingPolicies != null" (presumably it should be "matchingPolicies == null") at the start, which is always false. Therefore the method always returns null and the intended optimization goes unused.

---

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-8357682: sun.security.provider.certpath.Builder#getMatchingPolicies always returns null (Bug - P4)

Reviewers

• Sean Mullan (@seanjmullan - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 26418

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

Using diff file

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

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back koushikthirupattur! 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]

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

8357682: sun.security.provider.certpath.Builder#getMatchingPolicies always returns null

Reviewed-by: mullan

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 369 new commits pushed to the master branch:

• 4669005: 8361912: ThreadsListHandle::cv_internal_thread_to_JavaThread does not deal with a virtual thread's carrier thread
• 3e4e5dd: 8364081: Shenandoah & GenShen logging improvement
• ea0b49c: 8362979: C2 fails with unexpected node in SuperWord truncation: CmpLTMask, RoundF
• ... and 366 more: https://git.openjdk.org/jdk/compare/8ea544c33fc502208577249fb83544f8d876bc17...master

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. Possible candidates are the reviewers of this PR (@seanjmullan) but any other Committer may sponsor as well.

➡️ 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]

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

• security

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.

[mlbridge]

Webrevs

• 01: Full - Incremental (9e7508e1)
• 00: Full (861801a4)

[openjdk]

⚠️ @koushikthirupattur the full name on your profile does not match the author name in this pull requests' HEAD commit. If this pull request gets integrated then the author name from this pull requests' HEAD commit will be used for the resulting commit. If you wish to push a new commit with a different author name, then please run the following commands in a local repository of your personal fork:

$ git checkout 8357682
$ git commit --author='Preferred Full Name <[email protected]>' --allow-empty -m 'Update full name'
$ git push

[koushikthirupattur]

/integrate

[openjdk]

@koushikthirupattur
Your change (at version 9e7508e) is now ready to be sponsored by a Committer.

[seanjmullan]

/sponsor

[openjdk]

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

• 3bdac53: 8361212: Remove AffirmTrust root CAs
• 57d02d9: 8362279: [vectorapi] VECTOR_OP_SUADD needs reduction support
• a2e86ff: 8364037: Sort share includes: adlc, libadt, metaprogramming
• ... and 392 more: https://git.openjdk.org/jdk/compare/8ea544c33fc502208577249fb83544f8d876bc17...master

Your commit was automatically rebased without conflicts.

[openjdk]

@seanjmullan @koushikthirupattur Pushed as commit 413ac74.

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