From: Aleksa Sarai <asarai@suse.de>
To: Tejun Heo <tj@kernel.org>
Cc: Li Zefan <lizefan@huawei.com>,
Johannes Weiner <hannes@cmpxchg.org>,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
dev@opencontainers.org, Aleksa Sarai <cyphar@cyphar.com>
Subject: Re: [PATCH v3 1/2] cgroup: apply common ancestor cgroup.procs restriction in cgroupv1
Date: Tue, 3 May 2016 11:44:47 +1000 [thread overview]
Message-ID: <5728028F.5060906@suse.de> (raw)
In-Reply-To: <20160502160332.GQ7822@mtj.duckdns.org>
> So, you can't apply a new restriction like this retro-actively to
> cgroup v1 hierarchies.
Okay, understood. I'll see if it's possible to make this change safe
without adding restrictions to cgroupv1 hierarchies.
--
Aleksa Sarai
Software Engineer (Containers)
SUSE Linux GmbH
https://www.cyphar.com/
next prev parent reply other threads:[~2016-05-03 1:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 14:01 [PATCH v3 0/2] cgroup: allow management of subtrees by new cgroup namespaces Aleksa Sarai
2016-05-02 14:01 ` Aleksa Sarai
[not found] ` <1462197681-6879-1-git-send-email-asarai-l3A5Bk7waGM@public.gmane.org>
2016-05-02 14:01 ` [PATCH v3 1/2] cgroup: apply common ancestor cgroup.procs restriction in cgroupv1 Aleksa Sarai
2016-05-02 14:01 ` Aleksa Sarai
[not found] ` <1462197681-6879-2-git-send-email-asarai-l3A5Bk7waGM@public.gmane.org>
2016-05-02 16:03 ` Tejun Heo
2016-05-02 16:03 ` Tejun Heo
2016-05-03 1:44 ` Aleksa Sarai [this message]
2016-05-02 14:01 ` [PATCH v3 2/2] cgroup: allow management of subtrees by new cgroup namespaces Aleksa Sarai
2016-05-02 14:01 ` Aleksa Sarai
2016-05-02 16:06 ` Tejun Heo
[not found] ` <20160502160604.GR7822-qYNAdHglDFBN0TnZuCh8vA@public.gmane.org>
2016-05-03 1:52 ` Aleksa Sarai
2016-05-03 1:52 ` Aleksa Sarai
[not found] ` <57280456.1090106-l3A5Bk7waGM@public.gmane.org>
2016-05-03 15:55 ` Tejun Heo
2016-05-03 15:55 ` Tejun Heo
[not found] ` <20160503155511.GA7110-qYNAdHglDFBN0TnZuCh8vA@public.gmane.org>
2016-05-04 9:58 ` Aleksa Sarai
2016-05-04 9:58 ` Aleksa Sarai
2016-05-09 14:04 ` Aleksa Sarai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5728028F.5060906@suse.de \
--to=asarai@suse.de \
--cc=cgroups@vger.kernel.org \
--cc=cyphar@cyphar.com \
--cc=dev@opencontainers.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.