8370065: Windows perfmemory coding - use SetSecurityDescriptorControl directly

[MBaesken]

We have some 'at runtime' checks for availability of SetSecurityDescriptorControl in the Windows perfmemory coding. But those were done for very old Windows versions like Win98 and can probably be removed.
Looking at the description
https://learn.microsoft.com/en-us/windows/win32/api/securitybaseapi/nf-securitybaseapi-setsecuritydescriptorcontrol
it is available at least since Win2003/XP so the function can be called directly.

---

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-8370065: Windows perfmemory coding - use SetSecurityDescriptorControl directly (Enhancement - P4)

Reviewers

• David Holmes (@dholmes-ora - Reviewer)
• Thomas Stuefe (@tstuefe - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 27937

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

Using diff file

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

Using Webrev

Link to Webrev Comment

[bridgekeeper]

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

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

8370065: Windows perfmemory coding - use SetSecurityDescriptorControl directly

Reviewed-by: dholmes, stuefe

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

• dcf46a0: 8369658: Client emulation mode sets MaxRAM too late
• 027aea9: 8370325: G1: Disallow GC for TLAB allocation
• ffcb158: 8320677: Printer tests use invalid '@run main/manual=yesno
• ... and 10 more: https://git.openjdk.org/jdk/compare/65b32394187988abab99a8017eda39b1bd4a1782...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.

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

[openjdk]

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

• hotspot-runtime

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

• 00: Full (0112d237)

[dholmes-ora]

This seems fine.

Thanks.

[tstuefe]

good

[MBaesken]

Thanks for the reviews !

/integrate

[openjdk]

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

• 3fdb15f: 8369622: GlobalChunkPoolMutex is recursively locked during error handling
• 5a83d6a: 8370406: Parallel: Refactor ParCompactionManager::mark_and_push
• da968dc: 8370227: Migrate micros-javac benchmarks from jmh-jdk-microbenchmarks
• ... and 14 more: https://git.openjdk.org/jdk/compare/65b32394187988abab99a8017eda39b1bd4a1782...master

Your commit was automatically rebased without conflicts.

[openjdk]

@MBaesken Pushed as commit b597b65.

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