[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20160111182010.bc4e171b.akpm@linux-foundation.org>
Date: Mon, 11 Jan 2016 18:20:10 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Mike Kravetz <mike.kravetz@...cle.com>
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org,
Hugh Dickins <hughd@...gle.com>,
Naoya Horiguchi <n-horiguchi@...jp.nec.com>,
Hillf Danton <hillf.zj@...baba-inc.com>,
Davidlohr Bueso <dave@...olabs.net>,
Dave Hansen <dave.hansen@...ux.intel.com>
Subject: Re: [PATCH] mm/hugetlbfs: Unmap pages if page fault raced with hole
punch
On Mon, 11 Jan 2016 17:36:43 -0800 Mike Kravetz <mike.kravetz@...cle.com> wrote:
> >
> > I'll mark this patch as "pending, awaiting Mike's go-ahead".
> >
>
> When this patch was originally submitted, bugs were discovered in the
> hugetlb_vmdelete_list routine. So, the patch "Fix bugs in
> hugetlb_vmtruncate_list" was created.
>
> I have retested the changes in this patch specifically dealing with
> page fault/hole punch race on top of the new hugetlb_vmtruncate_list
> routine. Everything looks good.
>
> How would you like to proceed with the patch?
> - Should I create a series with the hugetlb_vmtruncate_list split out?
> - Should I respin with hugetlb_vmtruncate_list patch applied?
>
> Just let me know what is easiest/best for you.
If you're saying that
http://ozlabs.org/~akpm/mmots/broken-out/mm-mempolicy-skip-non-migratable-vmas-when-setting-mpol_mf_lazy.patch
and
http://ozlabs.org/~akpm/mmots/broken-out/mm-hugetlbfs-unmap-pages-if-page-fault-raced-with-hole-punch.patch
are the final everything-works versions then we're all good to go now.
Powered by blists - more mailing lists