On Wed, 26 Feb 2014 23:39:37 -0500 Naoya Horiguchi <n-horigu...@ah.jp.nec.com> wrote:
> vma_adjust() is called also for vma(VM_HUGETLB) and it could happen that > we happen to try to split hugetlbfs hugepage. So exclude the possibility. > It would be nice to have a more complete changelog here please. Under what circumstances does this cause problems and what are the user-observable effects? > --- next-20140220.orig/mm/mmap.c > +++ next-20140220/mm/mmap.c > @@ -772,7 +772,8 @@ again: remove_next = 1 + (end > > next->vm_end); > } > } > > - vma_adjust_trans_huge(vma, start, end, adjust_next); > + if (transparent_hugepage_enabled(vma)) > + vma_adjust_trans_huge(vma, start, end, adjust_next); > > anon_vma = vma->anon_vma; > if (!anon_vma && adjust_next) > -- > 1.8.5.3 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
