JDK-8287007 : [cgroups] Consistently use stringStream throughout parsing code
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 19
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: linux
  • Submitted: 2022-05-19
  • Updated: 2022-06-13
  • Resolved: 2022-06-13
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 20
20 masterFixed
Related Reports
Relates :  
JDK-8146115 - Improve docker container detection and resource configuration usage
Relates :  
JDK-8286212 - Cgroup v1 initialization causes NPE on some systems
Description
JDK-8146115 added code for parsing various proc files. There are also code snippets for assembling paths where the the controller's limit files actually are. We should change the string concatenation code to use stringStream consistently as this avoids writable buffers on the stack and doesn't have a hard-coded path max limit.

JDK-8286212 started this work for added code.
Comments
Changeset: e0baf012 Author: Severin Gehwolf <sgehwolf@openjdk.org> Date: 2022-06-13 15:14:51 +0000 URL: https://git.openjdk.org/jdk/commit/e0baf012b111e422ddf39a577b1b4af2599fd00d
13-06-2022
A pull request was submitted for review. URL: https://git.openjdk.java.net/jdk/pull/8969 Date: 2022-06-01 09:18:38 +0000
01-06-2022