8292083: Detected container memory limit may exceed physical machine memory

[jmtd]

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

The backport is not clean:

• unrelated changes in src/hotspot/os/linux/os_linux.hpp (slightly different to the 17u backport)
• in src /hotspot/os/linux/cgroupV1Subsystem_linux.cpp, the original patch modified
  CgroupV1Subsystem::kernel_memory_limit_in_bytes, which does not yet exist in jdk11u.
  It is introduced in 8287011. I don't know whether that will get backported to 11u 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/jdk11u-dev pull/1346/head:pull/1346
$ git checkout pull/1346

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 1346

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk11u-dev/pull/1346.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.

[openjdk]

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

[mlbridge]

Webrevs

• 00: Full (a6d05ce5)

[jerboaa]

Looks good.

[openjdk]

@jmtd This change now passes all automated pre-integration checks.

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 1 new commit pushed to the master branch:

• c9f3135: 8279385: [test] Adjust sun/security/pkcs12/KeytoolOpensslInteropTest.java after 8278344

Please see this link for an up-to-date comparison between the source branch of this pull request and 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.

[jmtd]

/integrate

[openjdk]

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

• 6e30d22: 8292887: Bump update version for OpenJDK: jdk-11.0.18
• 2f0f34c: 8291570: [TESTBUG] Part of JDK-8250984 absent from 11u
• 9186b3c: 8287463: JFR: Disable TestDevNull.java on Windows
• c9f3135: 8279385: [test] Adjust sun/security/pkcs12/KeytoolOpensslInteropTest.java after 8278344

Your commit was automatically rebased without conflicts.

[openjdk]

@jmtd Pushed as commit de91323.

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