mm/mm_init: don't subtract managed CMA pages twice

With hugetlb_cma_only, the "reserved" value in the "Memory:" boot message
can be wrong (small or underflowed).

When mem_init_print_info() calculates the reserved memory, it assumes that
no CMA pages are managed yet. However,  hugetlb may have already
initialized its bootmem CMA areas, so we end up subtracting them twice.

Fix it by only subtracting CMA pages that are not managed yet.

This has very low urgency, as it only affects a boot message.

Fixes: b1b7c045e808 ("mm/hugetlb: initialize gigantic bootmem hugepage struct pages earlier")
Signed-off-by: Chris Mason <mason@kernel.org>
[ david: improve description and comment ]
Signed-off-by: David Hildenbrand (Arm) <david@kernel.org>
Acked-by: Muchun Song (ByteDance) <muchun.song@linux.dev>
Link: https://patch.msgid.link/20261119-cma_managed-v1-1-385751505e24@kernel.org
Acked-by: Oscar Salvador (SUSE) <osalvador@kernel.org>
Signed-off-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
1 file changed