Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
8343191: Cgroup v1 subsystem fails to set subsystem path #21808
base: master
Are you sure you want to change the base?
8343191: Cgroup v1 subsystem fails to set subsystem path #21808
Changes from 1 commit
c1c7589
338f3e8
6a761ca
3bb779a
c808ad4
54fada4
30df5f0
f27175a
ec5fef0
b0a3c06
db97beb
60f1eea
2a7e9d8
70617c9
a3002a9
39f44e9
8e8ab86
28122ff
deca9d9
3568c13
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why this warning?
It appears it would make more sense to produce this warning when
cgroup_path
contains../
and falling back to themount_path
for the subsystem path which indicates we have acgroupns=private
deployment on CG v1, but would likely get away with it sincememory.limit_in_bytes
will be present at the mount root.If
cgroup_path
doesn't contain../
we should append thecgroup_path
to the_mount_point
similar to what we do for cg v2. In the cloudflare case we'd end up with a subsystem path of/sys/fs/cgroup/cpu,cpuacct/system.slice/garden.service/garden/bad/2f57368b-0eda-4e52-64d8-af5c
. Since thecgroup_path != _root
we trigger path adjustment increasing the chance to detect any lower limit in any of the paths down to the mount point.