linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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
Date: Fri, 9 Sep 2016 10:34:21 -0600	[thread overview]
Message-ID: <20160909163421.GB18554@linux.intel.com> (raw)
In-Reply-To: <20160909140327.r2j64s5xdaxnnxhx@thunk.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....

      reply	other threads:[~2016-09-09 16:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-19 11:19 DAX can not work on virtual nvdimm device Xiao Guangrong
2016-08-19 14:59 ` Dan Williams
2016-08-19 18:30   ` Ross Zwisler
2016-08-21  9:55     ` Boaz Harrosh
2016-08-29  7:54     ` Xiao Guangrong
2016-08-29 19:30       ` Ross Zwisler
2016-08-30  6:53         ` Xiao Guangrong
2016-08-30 17:09           ` Dan Williams
2016-08-31  8:44             ` Xiao Guangrong
2016-08-31 16:46               ` Ross Zwisler
2016-09-02  2:57               ` Ross Zwisler
2016-09-06 15:06                 ` Jan Kara
2016-09-08 20:47                   ` Ross Zwisler
2016-09-09  9:19                     ` Jan Kara
2016-09-09 14:03                       ` Theodore Ts'o
2016-09-09 16:34                         ` Ross Zwisler [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160909163421.GB18554@linux.intel.com \
    --to=ross.zwisler@linux.intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=guangrong.xiao@linux.intel.com \
    --cc=jack@suse.cz \
    --cc=kvm@vger.kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvdimm@ml01.01.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=tytso@mit.edu \
    --cc=yuhuang@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).