From: Dan Williams <dan.j.williams@intel.com>
To: Xiao Guangrong <guangrong.xiao@linux.intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>,
Linux ACPI <linux-acpi@vger.kernel.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
KVM <kvm@vger.kernel.org>,
"Zhang, Haozhong" <haozhong.zhang@intel.com>,
Yumei Huang <yuhuang@redhat.com>
Subject: Re: DAX can not work on virtual nvdimm device
Date: Fri, 19 Aug 2016 07:59:29 -0700 [thread overview]
Message-ID: <CAPcyv4hVgi6Hw8Beg=Nt78+U0QNJN9mBGWEp3V6bg86NaM3Q6Q@mail.gmail.com> (raw)
In-Reply-To: <436d7526-bf06-633d-afce-4333552d9e31@linux.intel.com>
On Fri, Aug 19, 2016 at 4:19 AM, Xiao Guangrong
<guangrong.xiao@linux.intel.com> wrote:
>
> Hi Dan,
>
> Recently, Redhat reported that nvml test suite failed on QEMU/KVM,
> more detailed info please refer to:
> https://bugzilla.redhat.com/show_bug.cgi?id=1365721
>
> The reason for this bug is that the memory region created by mmap()
> on the dax-based file was gone so that the region can not be found
> in /proc/self/smaps during the runtime.
>
> This is a simple way to trigger this issue:
> mount -o dax /dev/pmem0 /mnt/pmem/
> vim /mnt/pmem/xxx
> then 'vim' is crashed due to segment fault.
>
> This bug can be reproduced on your tree, the top commit is
> 10d7902fa0e82b (dax: unmap/truncate on device shutdown), the kernel
> configure file is attached.
>
> Your thought or comment is highly appreciated.
I'm going to be offline until Tuesday, but I will investigate when I'm
back. In the meantime if Ross or Vishal had an opportunity to take a
look I wouldn't say "no" :).
next prev parent reply other threads:[~2016-08-19 14:59 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 [this message]
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
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='CAPcyv4hVgi6Hw8Beg=Nt78+U0QNJN9mBGWEp3V6bg86NaM3Q6Q@mail.gmail.com' \
--to=dan.j.williams@intel.com \
--cc=guangrong.xiao@linux.intel.com \
--cc=haozhong.zhang@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-acpi@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=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).