8292083: Detected container memory limit may exceed physical machine memory

[jmtd]

This is a backport of 8292083 for jdk17u-dev. I wish to backport this to get the bug fix out
to JDK17 users as we have seen it in live deployments.

The backport is not clean:

• unrelated changes in src/hotspot/os/linux/os_linux.hpp
• in src /hotspot/os/linux/cgroupV1Subsystem_linux.cpp, the original patch modified
  CgroupV1Subsystem::kernel_memory_limit_in_bytes, which does not yet exist in jdk17u.
  It is introduced in 8287011. I don't know whether that will get backported to 17u in future.

---

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-8292083: Detected container memory limit may exceed physical machine memory

Reviewers

• Severin Gehwolf (@jerboaa - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev pull/646/head:pull/646
$ git checkout pull/646

Update a local copy of the PR:
$ git checkout pull/646
$ git pull https://git.openjdk.org/jdk17u-dev pull/646/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 646

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/646.diff

[bridgekeeper]

👋 Welcome back jdowland! 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.

[mlbridge]

Webrevs

• 00: Full (561fa331)

[jerboaa]

Please use Backport f694f8a7671002559e7d23fdb65d5e9c768f9c03 as the PR title, so that the bots recognize it as a backport.

[openjdk]

This backport pull request has now been updated with issue from the original commit.

[jerboaa]

Looks good to me.

[openjdk]

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

8292083: Detected container memory limit may exceed physical machine memory

Reviewed-by: sgehwolf

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 no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential 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.

[jmtd]

/integrate

[openjdk]

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

• 282efe5: 8292888: Bump update version for OpenJDK: jdk-17.0.6
• bf7e3bf: 8290456: remove os::print_statistics()
• 00445e8: 8288985: P11TlsKeyMaterialGenerator should work with ChaCha20-Poly1305
• d3197e7: 8287463: JFR: Disable TestDevNull.java on Windows

Your commit was automatically rebased without conflicts.

[openjdk]

@jmtd Pushed as commit e66fd86.

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