[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <e821d691-67f5-1f29-3c70-0bad13c8ad91@oracle.com>
Date: Thu, 12 Mar 2020 09:34:32 -0700 (PDT)
From: Mike Kravetz <mike.kravetz@...cle.com>
To: Qian Cai <cai@....pw>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Cc: 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>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 0/2] hugetlbfs: use i_mmap_rwsem for more synchronization
On 3/12/20 8:57 AM, Qian Cai wrote:
> On Wed, 2020-03-04 at 16:26 -0800, Mike Kravetz wrote:
>> While discussing the issue with huge_pte_offset [1], I remembered that
>> there were more outstanding hugetlb races. These issues are:
>
> Reverted this series on the top of today's linux-next fixed the hang with LTP
> move_pages12 on both powerpc and arm64,
>
> # /opt/ltp/testcases/bin/move_pages12
> tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
> move_pages12.c:263: INFO: Free RAM 260577280 kB
> move_pages12.c:281: INFO: Increasing 2048kB hugepages pool on node 0 to 4
> move_pages12.c:291: INFO: Increasing 2048kB hugepages pool on node 8 to 4
> move_pages12.c:207: INFO: Allocating and freeing 4 hugepages on node 0
> move_pages12.c:207: INFO: Allocating and freeing 4 hugepages on node 8
> <hang>
Thank you for finding this.
I'll dig into it. It is timing related as it takes a few test runs for
me to reproduce.
Sorry for the issues. Feel free to revert upstream and mm tree until
there is a resolution.
--
Mike Kravetz
Powered by blists - more mailing lists