summaryrefslogtreecommitdiff
path: root/NEWS
diff options
context:
space:
mode:
authorChris Down <chris@chrisdown.name>2019-05-03 08:32:41 -0400
committerChris Down <chris@chrisdown.name>2019-05-08 12:06:32 +0100
commit22bf131be278b95a4a204514d37a4344cf6365c6 (patch)
tree7173beb780c95e0bd92fb7f57df7e7f7e0df9d81 /NEWS
parent7e7223b3d57c950b399352a92e1d817f7c463602 (diff)
downloadsystemd-22bf131be278b95a4a204514d37a4344cf6365c6.tar.gz
cgroup: Support 0-value for memory protection directives
These make sense to be explicitly set at 0 (which has a different effect than the default, since it can affect processing of `DefaultMemoryXXX`). Without this, it's not easily possible to relinquish memory protection for a subtree, which is not great.
Diffstat (limited to 'NEWS')
-rw-r--r--NEWS3
1 files changed, 3 insertions, 0 deletions
diff --git a/NEWS b/NEWS
index 57ed27a61d..78c44db4a6 100644
--- a/NEWS
+++ b/NEWS
@@ -24,6 +24,9 @@ CHANGES WITH 243 in spe:
hierarchically set default memory protection values for a particular
subtree of the unit hierarchy.
+ * Memory protection directives can now take a value of zero, allowing
+ explicit opting out of a default value propagated by an ancestor.
+
CHANGES WITH 242: