Messages in this thread |  | | Subject | Re: [PATCH v4] mm/hugetlb: avoid hardcoding while checking if cma is enabled | From | Mike Kravetz <> | Date | Thu, 9 Jul 2020 20:11:38 -0700 |
| |
On 7/9/20 5:57 PM, Barry Song wrote: > hugetlb_cma[0] can be NULL due to various reasons, for example, node0 has > no memory. so NULL hugetlb_cma[0] doesn't necessarily mean cma is not > enabled. gigantic pages might have been reserved on other nodes. > This patch fixes possible double reservation and CMA leak. > > Fixes: cf11e85fc08c ("mm: hugetlb: optionally allocate gigantic hugepages using cma") > Cc: Mike Kravetz <mike.kravetz@oracle.com> > Cc: Jonathan Cameron <jonathan.cameron@huawei.com> > Acked-by: Roman Gushchin <guro@fb.com> > Signed-off-by: Barry Song <song.bao.hua@hisilicon.com>
Thank you!
Reviewed-by: Mike Kravetz <mike.kravetz@oracle.com>
-- Mike Kravetz
|  |