Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Wed, 19 Feb 2020 09:58:19 +0800
From:   Murphy Zhou <jencce.kernel@gmail.com>
To:     Jeff Moyer <jmoyer@redhat.com>
Cc:     Dan Williams <dan.j.williams@intel.com>,
        Murphy Zhou <jencce.kernel@gmail.com>,
        linux-nvdimm <linux-nvdimm@lists.01.org>,
        Jia He <justin.he@arm.com>, Linux MM <linux-mm@kvack.org>,
        "Shutemov, Kirill" <kirill.shutemov@intel.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: get rid of WARN if failed to cow user pages
Message-ID: <20200219015819.otdnknxpyo52txy7@xzhoux.usersys.redhat.com>
References: <20191225054227.gii6ctjkuddjnprs@xzhoux.usersys.redhat.com>
 <CAPcyv4hMPh0C+_OV+vuiYQikb8ZvRanna4vXfKN=10yrAyCjDA@mail.gmail.com>
 <x49imk3bo1h.fsf@segfault.boston.devel.redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <x49imk3bo1h.fsf@segfault.boston.devel.redhat.com>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Tue, Feb 18, 2020 at 04:09:30PM -0500, Jeff Moyer wrote:
> Dan Williams <dan.j.williams@intel.com> writes:
> 
> > [ drop Ross, add Kirill, linux-mm, and lkml ]
> >
> > On Tue, Dec 24, 2019 at 9:42 PM Murphy Zhou <jencce.kernel@gmail.com> wrote:
> >>
> >> By running xfstests with fsdax enabled, generic/437 always hits this
> >> warning[1] since this commit:
> >>
> >> commit 83d116c53058d505ddef051e90ab27f57015b025
> >> Author: Jia He <justin.he@arm.com>
> >> Date:   Fri Oct 11 22:09:39 2019 +0800
> >>
> >>     mm: fix double page fault on arm64 if PTE_AF is cleared
> >>
> >> Looking at the test program[2] generic/437 uses, it's pretty easy
> >> to hit this warning. Remove this WARN as it seems not necessary.
> >
> > This is not sufficient justification. Does this same test fail without
> > DAX? If not, why not? At a minimum you need to explain why this is not
> > indicating a problem.
> 
> I ran into this, too, and Kirill has posted a patch[1] to fix the issue.
> Note that it's a potential data corrupter, so just removing the warning
> is NOT the right approach.  :)

Agree :) Thanks!

> 
> -Jeff
> 
> [1] https://lore.kernel.org/linux-mm/20200218154151.13349-1-kirill.shutemov@linux.intel.com/T/#u
>