Re: [RFC PATCH 1/1] mm/hugetlb: clear compound_nr before freeing gigantic pages
From: Matthew Wilcox
Date: Tue Dec 08 2020 - 15:23:54 EST
On Tue, Dec 08, 2020 at 07:28:13PM +0100, Gerald Schaefer wrote:
> This is because only the compound_order is cleared in
> destroy_compound_gigantic_page(), and compound_nr is set to 1U << order == 1
> for order 0 in set_compound_order(page, 0).
I didn't realise there was a separate destroy path for gigantic pages.
Thanks for catching and fixing this.
Reviewed-by: Matthew Wilcox (Oracle) <willy@xxxxxxxxxxxxx>