Re: [PATCH v3] mm/hugetlb: avoid hardcoding while checking if cma is enable

[Andrew Morton]

On Tue, 7 Jul 2020 16:02:04 +1200 Barry Song <song.bao.hua@xxxxxxxxxxxxx> 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.

I'm trying to figure out whether this should be backported into 5.7.1,
but the changelog doesn't describe any known user-visible effects of
the bug.  Are there any?