Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936099AbcLUXy1 (ORCPT ); Wed, 21 Dec 2016 18:54:27 -0500 Received: from LGEAMRELO13.lge.com ([156.147.23.53]:43196 "EHLO lgeamrelo13.lge.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932878AbcLUXy0 (ORCPT ); Wed, 21 Dec 2016 18:54:26 -0500 X-Original-SENDERIP: 156.147.1.151 X-Original-MAILFROM: minchan@kernel.org X-Original-SENDERIP: 10.177.223.161 X-Original-MAILFROM: minchan@kernel.org Date: Thu, 22 Dec 2016 08:54:22 +0900 From: Minchan Kim To: Andreas Schwab Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, mbrugger@suse.de, linux-mm@kvack.org, Jason Evans Subject: Re: jemalloc testsuite stalls in memset Message-ID: <20161221235422.GA12727@bbox> References: <20161214235031.GA2912@bbox> <20161216063940.GA1334@bbox> <87d1gshscr.fsf@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87d1gshscr.fsf@suse.de> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1061 Lines: 33 Hello, Andreas Sorry for long delay. I was on vacation. On Fri, Dec 16, 2016 at 03:16:20PM +0100, Andreas Schwab wrote: > On Dez 16 2016, Minchan Kim wrote: > > > Below helps? > > > > diff --git a/mm/huge_memory.c b/mm/huge_memory.c > > index e10a4fe..dc37c9a 100644 > > --- a/mm/huge_memory.c > > +++ b/mm/huge_memory.c > > @@ -1611,6 +1611,7 @@ int madvise_free_huge_pmd(struct mmu_gather *tlb, struct vm_area_struct *vma, > > tlb->fullmm); > > orig_pmd = pmd_mkold(orig_pmd); > > orig_pmd = pmd_mkclean(orig_pmd); > > + orig_pmd = pmd_wrprotect(orig_pmd); > > > > set_pmd_at(mm, addr, pmd, orig_pmd); > > tlb_remove_pmd_tlb_entry(tlb, pmd, addr); > > Thanks, this fixes the issue (tested with 4.9). It was a quick hack to know what exact problem is there and your confirming helped a lot to understand the problem clear. More right approach is to support pmd dirty handling in general page fault handler rather than tweaking MADV_FREE. I just sent a new patch with Ccing you. Could you test it, please? Thanks!