From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: Ross Zwisler <ross.zwisler@linux.intel.com>,
Xiong Zhou <xzhou@redhat.com>,
linux-nvdimm@ml01.01.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: fsx tests on DAX started to fail with msync failure on 0307 -next tree
Date: Thu, 16 Mar 2017 09:53:35 -0600 [thread overview]
Message-ID: <20170316155335.GA27340@linux.intel.com> (raw)
In-Reply-To: <20170314173609.GA13885@linux.intel.com>
On Tue, Mar 14, 2017 at 11:36:10AM -0600, Ross Zwisler wrote:
> On Tue, Mar 14, 2017 at 10:56:42AM +0800, Xiong Zhou wrote:
> > Hi,
> >
> > xfstests cases:
> > generic/075 generic/112 generic/127 generic/231 generic/263
> >
> > fail with DAX, pass without it. Both xfs and ext4.
> >
> > It was okay on 0306 -next tree.
>
> Thanks for the report. I'm looking into it. -next is all kinds of broken.
> :(
Just FYI, in case folks are still testing -next:
One other issue that I was hitting was that for many of the commits in -next
kernel modules wouldn't load, which meant that my /dev/pmem0 device wasn't
showing up because I have libnvdimm compiled as a module.
I bisected that issue to this commit:
commit d1091c7fa3d5 ("objtool: Improve detection of BUG() and other dead
ends")
It looks like Xiong also found this issue:
https://lkml.org/lkml/2017/3/2/114
And Linus found it:
https://lkml.org/lkml/2017/2/28/794
- Ross
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-03-16 15:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 2:56 Xiong Zhou
2017-03-14 17:36 ` Ross Zwisler
2017-03-16 15:53 ` Ross Zwisler [this message]
2017-03-14 21:53 ` [PATCH] dax: fix regression in dax_writeback_mapping_range() 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=20170316155335.GA27340@linux.intel.com \
--to=ross.zwisler@linux.intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=xzhou@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