From: Toshi Kani Subject: Re: dax pmd fault handler never returns to userspace Date: Wed, 18 Nov 2015 15:04:41 -0700 Message-ID: <1447884281.21443.154.camel@hpe.com> References: <20151118170014.GB10656@linux.intel.com> <20151118182320.GA7901@linux.intel.com> <1447882389.21443.151.camel@hpe.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Ross Zwisler , linux-nvdimm , Ross Zwisler , linux-fsdevel , linux-ext4 To: Dan Williams Return-path: In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org 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. Thanks, -Toshi