[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <50CA830B.2050209@huawei.com>
Date: Fri, 14 Dec 2012 09:38:19 +0800
From: Jianguo Wu <wujianguo@...wei.com>
To: Michal Hocko <mhocko@...e.cz>
CC: "Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>,
<tj@...nel.org>, Li Zefan <lizefan@...wei.com>,
Andrew Morton <akpm@...ux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
<dhillf@...il.com>, Liujiang <jiang.liu@...wei.com>,
Jiang Liu <liuj97@...il.com>, qiuxishi <qiuxishi@...wei.com>,
Hanjun Guo <guohanjun@...wei.com>,
<linux-kernel@...r.kernel.org>, <linux-mm@...ck.org>,
<containers@...ts.linux-foundation.org>, <cgroups@...r.kernel.org>
Subject: Re: [PATCH v2 UPDATE] mm/hugetlb: create hugetlb cgroup file in hugetlb_init
On 2012/12/13 21:56, Michal Hocko wrote:
> On Thu 13-12-12 11:39:17, Jianguo Wu wrote:
>> Build kernel with CONFIG_HUGETLBFS=y,CONFIG_HUGETLB_PAGE=y
>> and CONFIG_CGROUP_HUGETLB=y, then specify hugepagesz=xx boot option,
>> system will boot fail.
>>
>> This failure is caused by following code path:
>> setup_hugepagesz
>> hugetlb_add_hstate
>> hugetlb_cgroup_file_init
>> cgroup_add_cftypes
>> kzalloc <--slab is *not available* yet
>>
>> For this path, slab is not available yet, so memory allocated will be
>> failed, and cause WARN_ON() in hugetlb_cgroup_file_init().
>>
>> So I move hugetlb_cgroup_file_init() into hugetlb_init().
>>
>> Changelog:
>> do code refactor as suggesting by Aneesh
>> add Reviewed-by and Acked-by
>>
>> Signed-off-by: Jianguo Wu <wujianguo@...wei.com>
>> Signed-off-by: Jiang Liu <jiang.liu@...wei.com>
>> Reviewed-by: Aneesh Kumar K.V <aneesh.kumar@...ux.vnet.ibm.com>
>> Acked-by: Michal Hocko <mhocko@...e.cz>
>
> Any reason to not add Cc: stable as I suggested earlier?
Hi Michal,
Sorry for forgot that.
Andrew has added Cc: stable when added to -mm tree.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists