From: Jan Kara <jack@suse.cz>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: sandeen@redhat.com, Jan Kara <jack@suse.cz>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
linux-nvdimm@lists.01.org, Dave Chinner <david@fromorbit.com>,
Christoph Hellwig <hch@lst.de>,
Lukas Czerner <lczerner@redhat.com>,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH v4 1/2] dax: dax_layout_busy_page() warn on !exceptional
Date: Fri, 24 Aug 2018 17:44:43 +0200 [thread overview]
Message-ID: <20180824154443.GA26549@quack2.suse.cz> (raw)
In-Reply-To: <20180813101252.GC8927@quack2.suse.cz>
On Mon 13-08-18 12:12:52, Jan Kara wrote:
> On Fri 10-08-18 22:10:53, Theodore Y. Ts'o wrote:
> > The generic/344 failure seems to be caused by a WARNING triggered in
> > the nvdimm code:
>
> OK, apparently this is nothing new for you as generic/344 fails for you
> even with 3.17. But it should not :). I'll try to see if I can reproduce
> this in my test setup during more test runs (I don't remember seeing it
> during occasional runs I do) and debug it further.
I could reproduce this relatively easily but it took me quite a while to
figure out how to best fix this. I'll send the fix shortly (mm: Fix warning
in insert_pfn()).
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
WARNING: multiple messages have this Message-ID (diff)
From: Jan Kara <jack-AlSwsSmVLrQ@public.gmane.org>
To: "Theodore Y. Ts'o" <tytso-3s7WtUTddSA@public.gmane.org>
Cc: sandeen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
Jan Kara <jack-AlSwsSmVLrQ@public.gmane.org>,
"Darrick J. Wong"
<darrick.wong-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>,
linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org,
Dave Chinner <david-FqsqvQoI3Ljby3iVrkZq2A@public.gmane.org>,
Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>,
Lukas Czerner <lczerner-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v4 1/2] dax: dax_layout_busy_page() warn on !exceptional
Date: Fri, 24 Aug 2018 17:44:43 +0200 [thread overview]
Message-ID: <20180824154443.GA26549@quack2.suse.cz> (raw)
In-Reply-To: <20180813101252.GC8927-4I4JzKEfoa/jFM9bn6wA6Q@public.gmane.org>
On Mon 13-08-18 12:12:52, Jan Kara wrote:
> On Fri 10-08-18 22:10:53, Theodore Y. Ts'o wrote:
> > The generic/344 failure seems to be caused by a WARNING triggered in
> > the nvdimm code:
>
> OK, apparently this is nothing new for you as generic/344 fails for you
> even with 3.17. But it should not :). I'll try to see if I can reproduce
> this in my test setup during more test runs (I don't remember seeing it
> during occasional runs I do) and debug it further.
I could reproduce this relatively easily but it took me quite a while to
figure out how to best fix this. I'll send the fix shortly (mm: Fix warning
in insert_pfn()).
Honza
--
Jan Kara <jack-IBi9RG/b67k@public.gmane.org>
SUSE Labs, CR
next prev parent reply other threads:[~2018-08-24 15:44 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 19:10 [PATCH v4 0/2] ext4: fix DAX dma vs truncate/hole-punch Ross Zwisler
2018-07-10 19:10 ` Ross Zwisler
2018-07-10 19:10 ` [PATCH v4 1/2] dax: dax_layout_busy_page() warn on !exceptional Ross Zwisler
2018-07-10 19:10 ` Ross Zwisler
2018-08-10 19:52 ` Eric Sandeen
2018-08-10 19:52 ` Eric Sandeen
2018-08-10 20:33 ` Theodore Y. Ts'o
2018-08-10 20:33 ` Theodore Y. Ts'o
2018-08-11 2:10 ` Theodore Y. Ts'o
2018-08-11 2:10 ` Theodore Y. Ts'o
2018-08-13 10:12 ` Jan Kara
2018-08-13 10:12 ` Jan Kara
2018-08-13 12:46 ` Theodore Y. Ts'o
2018-08-13 12:46 ` Theodore Y. Ts'o
2018-08-24 15:44 ` Jan Kara [this message]
2018-08-24 15:44 ` Jan Kara
2018-08-27 16:09 ` Jan Kara
2018-08-27 16:09 ` Jan Kara
2018-07-10 19:10 ` [PATCH v4 2/2] ext4: handle layout changes to pinned DAX mappings Ross Zwisler
2018-07-10 19:10 ` Ross Zwisler
2018-07-11 8:17 ` [PATCH v4 0/2] ext4: fix DAX dma vs truncate/hole-punch Jan Kara
2018-07-11 8:17 ` Jan Kara
2018-07-11 15:41 ` Ross Zwisler
2018-07-11 15:41 ` Ross Zwisler
2018-07-25 22:28 ` Ross Zwisler
2018-07-25 22:28 ` Ross Zwisler
2018-07-27 16:28 ` Ross Zwisler
2018-07-27 16:28 ` Ross Zwisler
2018-07-27 16:28 ` Ross Zwisler
2018-08-06 3:55 ` Dave Chinner
2018-08-06 3:55 ` Dave Chinner
2018-08-06 3:55 ` Dave Chinner
2018-08-06 15:49 ` Christoph Hellwig
2018-08-06 15:49 ` Christoph Hellwig
2018-08-06 15:49 ` Christoph Hellwig
2018-08-06 22:25 ` Dave Chinner
2018-08-06 22:25 ` Dave Chinner
2018-08-06 22:25 ` Dave Chinner
2018-08-07 8:45 ` Jan Kara
2018-08-07 8:45 ` Jan Kara
2018-08-07 8:45 ` Jan Kara
2018-09-10 22:18 ` Eric Sandeen
2018-09-10 22:18 ` Eric Sandeen
2018-09-10 22:18 ` Eric Sandeen
2018-09-11 15:14 ` Jan Kara
2018-09-11 15:14 ` Jan Kara
2018-09-11 15:14 ` Jan Kara
2018-09-11 15:20 ` Jan Kara
2018-09-11 15:20 ` Jan Kara
2018-09-11 15:20 ` Jan Kara
2018-09-11 17:28 ` Theodore Y. Ts'o
2018-09-11 17:28 ` Theodore Y. Ts'o
2018-09-11 17:28 ` Theodore Y. Ts'o
2018-09-11 18:21 ` Eric Sandeen
2018-09-11 18:21 ` Eric Sandeen
2018-09-11 18:21 ` Eric Sandeen
2018-07-31 19:44 ` Ross Zwisler
2018-07-31 19:44 ` 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=20180824154443.GA26549@quack2.suse.cz \
--to=jack@suse.cz \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.