summaryrefslogtreecommitdiffstats
path: root/mm/io-mapping.c
diff options
context:
space:
mode:
authorMike Kravetz <mike.kravetz@oracle.com>2022-12-12 15:50:41 -0800
committerAndrew Morton <akpm@linux-foundation.org>2022-12-21 14:31:52 -0800
commite700898fa075c69b3ae02b702ab57fb75e1a82ec (patch)
tree5f244c119f3eb4344f03a5b827adc254a71cded8 /mm/io-mapping.c
parent7ba594d700998bafa96a75360d2e060aa39156d2 (diff)
downloadlinux-e700898fa075c69b3ae02b702ab57fb75e1a82ec.tar.bz2
hugetlb: really allocate vma lock for all sharable vmas
Commit bbff39cc6cbc ("hugetlb: allocate vma lock for all sharable vmas") removed the pmd sharable checks in the vma lock helper routines. However, it left the functional version of helper routines behind #ifdef CONFIG_ARCH_WANT_HUGE_PMD_SHARE. Therefore, the vma lock is not being used for sharable vmas on architectures that do not support pmd sharing. On these architectures, a potential fault/truncation race is exposed that could leave pages in a hugetlb file past i_size until the file is removed. Move the functional vma lock helpers outside the ifdef, and remove the non-functional stubs. Since the vma lock is not just for pmd sharing, rename the routine __vma_shareable_flags_pmd. Link: https://lkml.kernel.org/r/20221212235042.178355-1-mike.kravetz@oracle.com Fixes: bbff39cc6cbc ("hugetlb: allocate vma lock for all sharable vmas") Signed-off-by: Mike Kravetz <mike.kravetz@oracle.com> Reviewed-by: Miaohe Lin <linmiaohe@huawei.com> Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> Cc: David Hildenbrand <david@redhat.com> Cc: James Houghton <jthoughton@google.com> Cc: Mina Almasry <almasrymina@google.com> Cc: Muchun Song <songmuchun@bytedance.com> Cc: Naoya Horiguchi <naoya.horiguchi@linux.dev> Cc: Peter Xu <peterx@redhat.com> Cc: <stable@vger.kernel.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'mm/io-mapping.c')
0 files changed, 0 insertions, 0 deletions