__tlb_adjust_range() takes the size of the range which has to be flushed
as an unsigned int. Its callers, tlb_flush_{pte,pmd,pud,p4d}_range(), get
and pass an unsigned long. Consequently, a range that is 4 GiB or larger
gets truncated, possibly to 0.
On arm64 with hugetlb, a 64k kernel can have 16 GiB hugetlb folios
mapped contiguously at the PMD level and flush them when unmapping, and a
16k kernel can flush 64 GiB PUDs through tlb_unshare_pmd_ptdesc(). So
at least these two scenarios are affected.
Fix it by flushing the proper range instead of the truncated one by
properly using "unsigned long" for range_size.
Fix generated by an LLM and sent by Josef Bacik in private.
Fixes: b528e4b640 ("mm/hugetlb: add tlb_remove_hugetlb_entry for handling hugetlb pages")
Fixes: 8ce720d5bd ("mm/hugetlb: fix excessive IPI broadcasts when unsharing PMD tables using mmu_gather")
Cc: [email protected]
Signed-off-by: Josef Bacik <[email protected]>
Acked-by: Lorenzo Stoakes (ARM) <[email protected]>
[ david: use two-tab indent, simplify description ]
Reviewed-by: Qi Zheng <[email protected]>
Reviewed-by: Gregory Price (Meta) <[email protected]>
Tested-by: Gregory Price (Meta) <[email protected]>
Reviewed-by: Dev Jain <[email protected]>
Reviewed-by: Muchun Song <[email protected]>
Reviewed-by: Pedro Falcato <[email protected]>
Reviewed-by: SJ Park <[email protected]>
Tested-by: Muhammad Usama Anjum <[email protected]>
Link: https://patch.msgid.link/[email protected]
Signed-off-by: David Hildenbrand (Arm) <[email protected]>