From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752907AbcIIQec (ORCPT <rfc822;w@1wt.eu>);
        Fri, 9 Sep 2016 12:34:32 -0400
Received: from mga04.intel.com ([192.55.52.120]:54563 "EHLO mga04.intel.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1750882AbcIIQe3 (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 9 Sep 2016 12:34:29 -0400
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.30,305,1470726000"; 
   d="scan'208";a="1053692739"
Date: Fri, 9 Sep 2016 10:34:21 -0600
From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: "Theodore Ts'o" <tytso@mit.edu>, Jan Kara <jack@suse.cz>,
        Ross Zwisler <ross.zwisler@linux.intel.com>,
        Xiao Guangrong <guangrong.xiao@linux.intel.com>,
        linux-ext4@vger.kernel.org, Dan Williams <dan.j.williams@intel.com>,
        Yumei Huang <yuhuang@redhat.com>, KVM <kvm@vger.kernel.org>,
        "linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>,
        "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
        LKML <linux-kernel@vger.kernel.org>,
        Linux ACPI <linux-acpi@vger.kernel.org>,
        Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: DAX can not work on virtual nvdimm device
Message-ID: <20160909163421.GB18554@linux.intel.com>
References: <600ac51c-0f61-6e53-9bfa-669c85494d1f@linux.intel.com>
 <20160829193014.GB16738@linux.intel.com>
 <61d5c470-a8bf-86d5-d1fe-b4b577a85967@linux.intel.com>
 <CAPcyv4hrFSxNcmmVLVZT4fK3+hspPCDKW0rVBj1=3GkJRgZ29Q@mail.gmail.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>
 <20160909140327.r2j64s5xdaxnnxhx@thunk.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160909140327.r2j64s5xdaxnnxhx@thunk.org>
User-Agent: Mutt/1.7.0 (2016-08-17)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Fri, Sep 09, 2016 at 10:03:27AM -0400, Theodore Ts'o wrote:
> 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?

It's from djbw's libnvdimm tree.

https://git.kernel.org/cgit/linux/kernel/git/djbw/nvdimm.git/

I don't think that commit is relevant, though.  I believe this should
reproduce with a vanilla v4.7 tree.  I can verify if you'd like.

> > 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?

I'm not sure if we've ever tested Centos6/RHEL6 with DAX.  It could be that it
has never worked.

> Or it's possible that Red Hat did something weird with the CentOS 6
> e2fsprogs....