From: Toshi Kani Subject: Re: dax pmd fault handler never returns to userspace Date: Wed, 18 Nov 2015 18:05:09 -0700 Message-ID: <1447895109.21443.169.camel@hpe.com> References: <20151118170014.GB10656@linux.intel.com> <20151118182320.GA7901@linux.intel.com> <1447882389.21443.151.camel@hpe.com> <1447884281.21443.154.camel@hpe.com> <20151119003624.GA26287@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Dan Williams , linux-nvdimm , Ross Zwisler , linux-fsdevel , linux-ext4 To: Ross Zwisler Return-path: In-Reply-To: <20151119003624.GA26287@linux.intel.com> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org On Wed, 2015-11-18 at 17:36 -0700, Ross Zwisler wrote: > On Wed, Nov 18, 2015 at 03:04:41PM -0700, Toshi Kani wrote: > > On Wed, 2015-11-18 at 13:57 -0800, Dan Williams wrote: > > > On Wed, Nov 18, 2015 at 1:33 PM, Toshi Kani wrote: > > > > I am seeing a similar/same problem in my test. I think the problem is > > > > that in case of a WP fault, wp_huge_pmd() -> __dax_pmd_fault() -> > > > > vmf_insert_pfn_pmd(), which is a no-op since the PMD is mapped already. > > > > We need WP handling for this PMD map. > > > > > > > > If it helps, I have attached change for follow_trans_huge_pmd(). I have > > > > not tested much, though. > > > > > > Interesting, I didn't get this far because my tests were crashing the > > > kernel. I'll add this case the pmd fault test in ndctl. > > > > I hit this one with mmap(MAP_POPULATE). With this change, I then hit the WP > > fault loop when writing to the range. > > Here's a fix - please let me know if this seems incomplete or incorrect for > some reason. My test looks working now. :-) I will do more testing and submit the gup patch as well. Thanks, -Toshi