From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752014AbcIIOGH (ORCPT ); Fri, 9 Sep 2016 10:06:07 -0400 Received: from imap.thunk.org ([74.207.234.97]:33008 "EHLO imap.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751038AbcIIOGE (ORCPT ); Fri, 9 Sep 2016 10:06:04 -0400 Date: Fri, 9 Sep 2016 10:03:27 -0400 From: "Theodore Ts'o" To: Jan Kara Cc: Ross Zwisler , Xiao Guangrong , linux-ext4@vger.kernel.org, Dan Williams , Yumei Huang , KVM , "linux-nvdimm@lists.01.org" , "qemu-devel@nongnu.org" , LKML , Linux ACPI , Stefan Hajnoczi Subject: Re: DAX can not work on virtual nvdimm device Message-ID: <20160909140327.r2j64s5xdaxnnxhx@thunk.org> Mail-Followup-To: Theodore Ts'o , Jan Kara , Ross Zwisler , Xiao Guangrong , linux-ext4@vger.kernel.org, Dan Williams , Yumei Huang , KVM , "linux-nvdimm@lists.01.org" , "qemu-devel@nongnu.org" , LKML , Linux ACPI , Stefan Hajnoczi References: <20160819183047.GA7216@linux.intel.com> <600ac51c-0f61-6e53-9bfa-669c85494d1f@linux.intel.com> <20160829193014.GB16738@linux.intel.com> <61d5c470-a8bf-86d5-d1fe-b4b577a85967@linux.intel.com> <25098f37-53f7-6d5d-0b1a-8469bab51a9f@linux.intel.com> <20160902025738.GA26108@linux.intel.com> <20160906150620.GJ28922@quack2.suse.cz> <20160908204708.GA15167@linux.intel.com> <20160909091925.GF22777@quack2.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160909091925.GF22777@quack2.suse.cz> User-Agent: Mutt/1.6.2-neo (2016-07-23) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: tytso@thunk.org X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Sep 09, 2016 at 11:19:25AM +0200, Jan Kara wrote: > > > > > 1. make the guest kernel based on your tree, the top commit is > > > > > 10d7902fa0e82b (dax: unmap/truncate on device shutdown) and > > > > > the config file can be found in this thread. What git tree is 10d7902fa0e82b from? > Hum, nothing unusual in there. I've tried reproducing on a local SLE11 SP3 > machine (which is from about the same time) but everything works as > expected there. Shrug... I just tried reproducing it via "gce-xfstests --pmem-device shell" with a downgraded e2fsprogs to stock upstream 1.42.12, and I can't reproduce it with the ext4.git tree. I'm not sure whether the git commit is critical, though. Is this a regression that was working before? Or it's possible that Red Hat did something weird with the CentOS 6 e2fsprogs.... - Ted