On Thu, 27 Jan 2011 09:08:51 +0800 Li Zefan<lizf@xxxxxxxxxxxxxx> wrote:
Andrew Morton wrote:ooh, that was clever of me.On Tue, 25 Jan 2011 10:39:48 +0100Because you wanted to wait for some time for users (if any) to notice this
Daniel Lezcano<daniel.lezcano@xxxxxxx> wrote:
This patch removes the ns_cgroup as suggested in the following thread:I had this patch queued up in September last year, but dropped it. Why
did I do that?
Author: Daniel Lezcano<daniel.lezcano@xxxxxxx>
Date: Wed Oct 27 15:33:38 2010 -0700
cgroup: notify ns_cgroup deprecated
The ns_cgroup will be removed very soon. Let's warn, for this version,
ns_cgroup is deprecated.
Make ns_cgroup and clone_children exclusive. If the clone_children is set
and the ns_cgroup is mounted, let's fail with EINVAL when the ns_cgroup
subsys is created (a printk will help the user to understand why the
Update the feature remove schedule file with the deprecated ns_cgroup.
Signed-off-by: Daniel Lezcano<daniel.lezcano@xxxxxxx>
Acked-by: Paul Menage<menage@xxxxxxxxxx>
Signed-off-by: Andrew Morton<akpm@xxxxxxxxxxxxxxxxxxxx>
Signed-off-by: Linus Torvalds<torvalds@xxxxxxxxxxxxxxxxxxxx>
Here is the text which was missing from the changelog:
This is a userspace-visible change. Commit 45531757b45c ("cgroup:
notify ns_cgroup deprecated") (merged into 2.6.27) caused the kernel
to emit a printk warning users that the feature is planned for
removal. Since that time we have heard from XXX users who were
affected by this.
Please provide XXX.
How do we know that 2.6.37->2.6.38 is long enough? Will any major
distros be released containing this warning in that timeframe? I doubt