[PATCH] hugetlb_cgroup: explicitly init the early_init field
Hillf Danton
dhillf at gmail.com
Tue Apr 22 06:47:42 UTC 2014
On Tue, Apr 22, 2014 at 1:30 PM, Jianyu Zhan <nasa4836 at gmail.com> wrote:
> For a cgroup subsystem who should init early, then it should carefully
> take care of the implementation of css_alloc, because it will be called
> before mm_init() setup the world.
>
> Luckily we don't, and we better explicitly assign the early_init field
> to 0, for document reason.
>
But other fields still missed, if any. Fair?
> Signed-off-by: Jianyu Zhan <nasa4836 at gmail.com>
> ---
> mm/hugetlb_cgroup.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/mm/hugetlb_cgroup.c b/mm/hugetlb_cgroup.c
> index 595d7fd..b5368f8 100644
> --- a/mm/hugetlb_cgroup.c
> +++ b/mm/hugetlb_cgroup.c
> @@ -405,4 +405,5 @@ struct cgroup_subsys hugetlb_cgrp_subsys = {
> .css_alloc = hugetlb_cgroup_css_alloc,
> .css_offline = hugetlb_cgroup_css_offline,
> .css_free = hugetlb_cgroup_css_free,
> + .early_init = 0,
> };
> --
> 2.0.0-rc0
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
More information about the Containers
mailing list