RFR: 8263476: NMT: Stack guard pages should not be marked as committed

Thu Jul 31 10:43:26 UTC 2025

Use reserved (instead of committed) memory for stack-guard-pages on linux like systems.

`os::must_commit_stack_guard_pages` uses `commit` in its name, but `commit` usually has specific meanings in OS memory context. The actual question the caller is asking is whether the caller needs to do some preparation work before marking the guard-pages as inaccessible. To avoid confusion, I changed it to "allocate". Other suggestions are welcome.

Test: tier1-3

-------------

Commit messages:
 - no-commit-stack-guard-page

Changes: https://git.openjdk.org/jdk/pull/26571/files
  Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=26571&range=00
  Issue: https://bugs.openjdk.org/browse/JDK-8263476
  Stats: 25 lines in 8 files changed: 3 ins; 8 del; 14 mod
  Patch: https://git.openjdk.org/jdk/pull/26571.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/26571/head:pull/26571

PR: https://git.openjdk.org/jdk/pull/26571