From: Dave Chinner <david@fromorbit.com>
To: Ross Zwisler <ross.zwisler@linux.intel.com>,
xfs@oss.sgi.com, Brian Foster <bfoster@redhat.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Jeff Moyer <jmoyer@redhat.com>
Subject: Re: xfstests failures with xfs, dax and v4.4-rc3
Date: Fri, 11 Dec 2015 09:33:33 +1100 [thread overview]
Message-ID: <20151210223333.GH26718@dastard> (raw)
In-Reply-To: <20151210165458.GA13603@linux.intel.com>
On Thu, Dec 10, 2015 at 09:54:58AM -0700, Ross Zwisler wrote:
> On Wed, Dec 02, 2015 at 02:39:32PM -0700, Ross Zwisler wrote:
> > On Thu, Dec 03, 2015 at 07:45:02AM +1100, Dave Chinner wrote:
> > > On Thu, Dec 03, 2015 at 07:29:10AM +1100, Dave Chinner wrote:
> > > > On Wed, Dec 02, 2015 at 11:34:38AM -0700, Ross Zwisler wrote:
> > > > > I'm hitting a few more test failures in my testing setup with v4.4-rc3, xfs
> > > > > and DAX. My test setup is a pair of 4GiB PMEM partitions in a KVM virtual
> > > > > machine. Here are the failures:
> > > >
> > > > Which are caused by commit 1ca1915 ("xfs: Don't use unwritten extents
> > > > for DAX") because of this code for unwritten extent conversion in
> > > > get_blocks:
> > > >
> > > > tp->t_flags |= XFS_TRANS_RESERVE;
> > > >
> > > > It's a minor problem compared to all the other issues DAX has right
> > > > now, so I ignored it to get the bigger problem solved first.
> > >
> > > Patch to fix the problem below.
> > >
> > > -Dave.
> > > --
> > > Dave Chinner
> > > david@fromorbit.com
> > >
> > > xfs: Don't use reserved blocks for data blocks with DAX
> > >
> > > From: Dave Chinner <dchinner@redhat.com>
> > >
> > > Commit 1ca1915 ("xfs: Don't use unwritten extents for DAX") enabled
> > > the DAX allocation call to dip into the reserve pool in case it was
> > > converting unwritten extents rather than allocating blocks. This was
> > > a direct copy of the unwritten extent conversion code, but had an
> > > unintended side effect of allowing normal data block allocation to
> > > use the reserve pool. Hence normal block allocation could deplete
> > > the reserve pool and prevent unwritten extent conversion at ENOSPC,
> > > hence violating fallocate guarantees on preallocated space.
> > >
> > > Fix it by checking whether the incoming map from __xfs_get_blocks()
> > > spans an unwritten extent and only use the reserve pool if the
> > > allocation covers an unwritten extent.
> > >
> > > Signed-off-by: Dave Chinner <dchinner@redhat.com>
> >
> > Tested-by: Ross Zwisler <ross.zwisler@linux.intel.com>
> >
> > I've verified that this fixes all three failing xfstests reported in this mail.
> > Thanks!
>
> Hey Dave,
>
> Are you planning on pushing this fix for v4.4?
No plans to right now - ENOSPC is a corner case that most users
won't be anywhere near, especially for experimental functionality on
hardware nobody actually has....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2015-12-10 22:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 18:34 xfstests failures with xfs, dax and v4.4-rc3 Ross Zwisler
2015-12-02 20:10 ` Dan Williams
2015-12-02 20:29 ` Dave Chinner
2015-12-02 20:45 ` Dave Chinner
2015-12-02 21:39 ` Ross Zwisler
2015-12-10 16:54 ` Ross Zwisler
2015-12-10 22:33 ` Dave Chinner [this message]
2015-12-11 4:26 ` Ross Zwisler
2015-12-14 0:20 ` Dave Chinner
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=20151210223333.GH26718@dastard \
--to=david@fromorbit.com \
--cc=bfoster@redhat.com \
--cc=jmoyer@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ross.zwisler@linux.intel.com \
--cc=xfs@oss.sgi.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).