From: Dave Jiang <dave.jiang@intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Xiong Zhou <xzhou@redhat.com>
Cc: linux-nvdimm@ml01.01.org, "Zwisler,
Ross" <ross.zwisler@intel.com>,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
linux-fsdevel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: linux-next 0112 tree breaks fs DAX
Date: Tue, 17 Jan 2017 13:25:07 -0700 [thread overview]
Message-ID: <b95fcdd4-9537-9b4c-e821-4043f1a944ad@intel.com> (raw)
In-Reply-To: <711fc876-c805-8483-a6af-f4e3c8369084@intel.com>
On 01/17/2017 11:13 AM, Dave Jiang wrote:
>
>
> On 01/17/2017 09:05 AM, Dave Jiang wrote:
>> On 01/16/2017 03:45 AM, Stephen Rothwell wrote:
>>> Hi Xiong,
>>>
>>> Just cc'ing Andrew.
>>>
>>> On Mon, 16 Jan 2017 17:29:16 +0800 Xiong Zhou <xzhou@redhat.com> wrote:
>>>>
>>>> On Fri, Jan 13, 2017 at 06:16:41PM +0800, Xiong Zhou wrote:
>>>>> Hi,
>>>>>
>>>>> These cases "hang" when testing with -o dax mount option:
>>>>> xfstests generic/030 generic/34{0,4,5,6} generic/198
>>>>> (maybe more)
>>>>>
>>>>> The test programme holetest or aiodio keep running for a
>>>>> long time. It's killable, but it seems never return.
>>>>>
>>>>> With both ext4 and xfs as fs.
>>>>>
>>>>> Without -o dax mount option, cases pass in seconds.
>>>>>
>>>>> 0111 tree passed the tests.
>>>>>
>>>>> sh-4.2# git log --oneline next-20170111..next-20170112 fs/dax.c
>>>>> 0c9a7909dd13 mm, dax: change pmd_fault() to take only vmf parameter
>>>>> f8dbc198d4ea mm, dax: make pmd_fault() and friends be the same as fault()
>>>>
>>>> 0112 tree with above 2 commits reverted pass the tests.
>>>
>>
>> Thanks. I will debug.
>>
>
> Xiong,
> I think I reproduced the issue, but only on the second commit
> 0c9a7909dd13 and not the first one f8dbc198d4ea. Can you please confirm
> that "f8dbc198d4ea mm, dax: make pmd_fault() and friends be the same as
> fault()" is ok or the failure starts with that? Thanks!
Actually nevermind. I am able to reproduce on the first commit now. Thanks.
prev parent reply other threads:[~2017-01-17 20:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 10:16 linux-next 0112 tree breaks fs DAX Xiong Zhou
2017-01-16 9:29 ` Xiong Zhou
2017-01-16 10:45 ` Stephen Rothwell
2017-01-17 16:05 ` Dave Jiang
2017-01-17 18:13 ` Dave Jiang
2017-01-17 20:25 ` Dave Jiang [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=b95fcdd4-9537-9b4c-e821-4043f1a944ad@intel.com \
--to=dave.jiang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=ross.zwisler@intel.com \
--cc=sfr@canb.auug.org.au \
--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;
as well as URLs for NNTP newsgroup(s).