From: Christian Brauner Date: Sat, 17 Feb 2018 18:43:46 +0000 (+0100) Subject: cgfsng: __cg_unified_attach() X-Git-Tag: lxc-2.0.10~274 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=8f975b98e4c1f33ac6dec606d5e9e3c8602c8a38;p=thirdparty%2Flxc.git cgfsng: __cg_unified_attach() Signed-off-by: Christian Brauner --- diff --git a/src/lxc/cgroups/cgfsng.c b/src/lxc/cgroups/cgfsng.c index 48229f200..db799877f 100644 --- a/src/lxc/cgroups/cgfsng.c +++ b/src/lxc/cgroups/cgfsng.c @@ -2393,10 +2393,10 @@ static inline char *build_full_cgpath_from_monitorpath(struct hierarchy *h, return must_make_path(h->mountpoint, inpath, filename, NULL); } -/* Technically, we're always at a delegation boundary here. (This is especially - * true when cgroup namespaces are available.) The reasoning is that in order +/* Technically, we're always at a delegation boundary here (This is especially + * true when cgroup namespaces are available.). The reasoning is that in order * for us to have been able to start a container in the first place the root - * cgroup must have been a leaf node. Now, either the container's init system + * cgroup must have been a leaf node. Now, either the container's init system * has populated the cgroup and kept it as a leaf node or it has created * subtrees. In the former case we will simply attach to the leaf node we * created when we started the container in the latter case we create our own