linux-kernel - Re: linux-next 0112 tree breaks fs DAX

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <b95fcdd4-9537-9b4c-e821-4043f1a944ad@intel.com>
Date:   Tue, 17 Jan 2017 13:25:07 -0700
From:   Dave Jiang <dave.jiang@...el.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Xiong Zhou <xzhou@...hat.com>
Cc:     linux-nvdimm@...1.01.org, "Zwisler, Ross" <ross.zwisler@...el.com>,
        linux-kernel@...r.kernel.org, linux-next@...r.kernel.org,
        linux-fsdevel@...r.kernel.org,
        Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: linux-next 0112 tree breaks fs DAX

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@...hat.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.