Under the hood
Useful1 Signal2
On Linux, a process already inside a managed memory group is reported as covered rather than getting a new one.
What's wrong with this entry?
Anonymous. No account, no email.
What
The Linux memory-limit reader now reports "covered" when the process's control group path already contains the marker segment it looks for, instead of going on to work out a new group directory to create. Applies to both the older memory-controller layout and the current unified one.
Evidence
"covered"
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.236
macOS sandbox re-applies read and delete denials inside writable folders
Both mention sandbox
-
v2.1.236
Sandbox proxy no longer writes to sockets that have gone away
Both mention sandbox
-
v2.1.236
IPv6 hosts through the proxy
Both mention sandbox