linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: Dave Chinner <david@fromorbit.com>
Cc: "Matthew Wilcox" <willy@infradead.org>,
	linux-xfs <linux-xfs@vger.kernel.org>,
	"Linux MM" <linux-mm@kvack.org>,
	"Jérôme Glisse" <jglisse@redhat.com>,
	"Christian König" <christian.koenig@amd.com>,
	"Jan Kara" <jack@suse.cz>,
	"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: [BUG, TOT] xfs w/ dax failure in __follow_pte_pmd()
Date: Thu, 3 Jan 2019 11:11:49 -0800	[thread overview]
Message-ID: <CAPcyv4jTWyYLEn+NcmVObscB9hArdsfxNL0YSMrHi_QDCOEkfQ@mail.gmail.com> (raw)
In-Reply-To: <20190103000354.GM4205@dastard>

On Wed, Jan 2, 2019 at 4:04 PM Dave Chinner <david@fromorbit.com> wrote:
>
> On Wed, Jan 02, 2019 at 02:50:05PM -0800, Matthew Wilcox wrote:
> > On Wed, Jan 02, 2019 at 01:25:31PM -0800, Matthew Wilcox wrote:
> > > On Thu, Jan 03, 2019 at 08:13:32AM +1100, Dave Chinner wrote:
> > > > Hi folks,
> > > >
> > > > An overnight test run on a current TOT kernel failed generic/413
> > > > with the following dmesg output:
> > > >
> > > > [ 9487.276402] RIP: 0010:__follow_pte_pmd+0x22d/0x340
> > > > [ 9487.305065] Call Trace:
> > > > [ 9487.307310]  dax_entry_mkclean+0xbb/0x1f0
> > >
> > > We've only got one commit touching dax_entry_mkclean and it's Jerome's.
> > > Looking through ac46d4f3c43241ffa23d5bf36153a0830c0e02cc, I'd say
> > > it's missing a call to mmu_notifier_range_init().
> >
> > Could I persuade you to give this a try?
>
> Yup, that fixes it.
>
> And looking at the code, the dax mmu notifier code clearly wasn't
> tested. i.e. dax_entry_mkclean() is the *only* code that exercises
> the conditional range parameter code paths inside
> __follow_pte_pmd().  This means it wasn't tested before it was
> proposed for inclusion and since inclusion no-one using -akpm,
> linux-next or the current mainline TOT has done any filesystem DAX
> testing until I tripped over it.
>
> IOws, this is the second "this was never tested before it was merged
> into mainline" XFS regression that I've found in the last 3 weeks.
> Both commits have been merged through the -akpm tree, and that
> implies we currently have no significant filesystem QA coverage on
> changes being merged through this route. This seems like an area
> that needs significant improvement to me....

Yes, this is also part of a series I explicitly NAK'd [1] because
there are no upstream users for it. I didn't bother to test it because
I thought the NAK was sufficient.

Andrew, any reason to not revert the set? They provide no upstream
value and actively break DAX.

[1]: https://www.spinics.net/lists/linux-fsdevel/msg137309.html

  reply	other threads:[~2019-01-03 19:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-02 21:13 [BUG, TOT] xfs w/ dax failure in __follow_pte_pmd() Dave Chinner
2019-01-02 21:25 ` Matthew Wilcox
2019-01-02 22:50   ` Matthew Wilcox
2019-01-03  0:03     ` Dave Chinner
2019-01-03 19:11       ` Dan Williams [this message]
2019-01-03 19:19         ` Andrew Morton
2019-01-03 20:25           ` Dan Williams
2019-01-03 19:30         ` Jerome Glisse

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=CAPcyv4jTWyYLEn+NcmVObscB9hArdsfxNL0YSMrHi_QDCOEkfQ@mail.gmail.com \
    --to=dan.j.williams@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=christian.koenig@amd.com \
    --cc=david@fromorbit.com \
    --cc=jack@suse.cz \
    --cc=jglisse@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=willy@infradead.org \
    /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).