[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20181218141053.e2725111ce5cc91493efab5f@linux-foundation.org>
Date: Tue, 18 Dec 2018 14:10:53 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Mike Kravetz <mike.kravetz@...cle.com>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@...ux.ibm.com>,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
Michal Hocko <mhocko@...nel.org>,
Hugh Dickins <hughd@...gle.com>,
Naoya Horiguchi <n-horiguchi@...jp.nec.com>,
"Aneesh Kumar K . V" <aneesh.kumar@...ux.vnet.ibm.com>,
Andrea Arcangeli <aarcange@...hat.com>,
"Kirill A . Shutemov" <kirill.shutemov@...ux.intel.com>,
Davidlohr Bueso <dave@...olabs.net>,
Prakash Sangappa <prakash.sangappa@...cle.com>,
stable@...r.kernel.org
Subject: Re: [PATCH 2/3] hugetlbfs: Use i_mmap_rwsem to fix page
fault/truncate race
On Mon, 17 Dec 2018 16:17:52 -0800 Mike Kravetz <mike.kravetz@...cle.com> wrote:
> ...
>
> > As you suggested in a comment to the subsequent patch, it would be better to
> > combine the patches and remove the dead code when it becomes dead. I will
> > work on that. Actually some of the code in patch 3 applies to patch 1 and
> > some applies to patch 2. So, it will not be simply combining patch 2 and 3.
>
> On second thought, the cleanups in patch 3 only apply to patch 2. So, just
> combining those two patches with a slightly updated commit message as below
> makes the most sense.
All confused. I dropped the current version, let's try again.
This:
> Hoping to get more comments on the overall direction and locking changes
> of this and the previous patch.
and this:
> Cc: <stable@...r.kernel.org>
> Fixes: ebed4bfc8da8 ("hugetlb: fix absurd HugePages_Rsvd")
make for a hot combination. Could people please prioritize review of
this code?
Perhaps a refresh and resend is in order.
Powered by blists - more mailing lists