From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Brian Foster <bfoster@redhat.com>,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com,
Jeff Moyer <jmoyer@redhat.com>,
linux-fsdevel@vger.kernel.org,
Ross Zwisler <ross.zwisler@linux.intel.com>
Subject: Re: xfstests failures with xfs, dax and v4.4-rc3
Date: Thu, 10 Dec 2015 21:26:09 -0700 [thread overview]
Message-ID: <20151211042609.GA5360@linux.intel.com> (raw)
In-Reply-To: <20151210223333.GH26718@dastard>
On Fri, Dec 11, 2015 at 09:33:33AM +1100, Dave Chinner wrote:
> 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:
> > > 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....
Really? I realize that it may be a case that most users won't actually hit,
but it is a 5 line change that fixes four xfstests regressions between v4.3 and
v4.4 for my DAX testing...
Is there a strong reason *not* to push it in the v4.4 cycle? I'm trying to
clear up all xfstests differences between DAX and non-DAX, and this would help
quite a bit.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: Dave Chinner <david@fromorbit.com>
Cc: 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: Thu, 10 Dec 2015 21:26:09 -0700 [thread overview]
Message-ID: <20151211042609.GA5360@linux.intel.com> (raw)
In-Reply-To: <20151210223333.GH26718@dastard>
On Fri, Dec 11, 2015 at 09:33:33AM +1100, Dave Chinner wrote:
> 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:
> > > 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....
Really? I realize that it may be a case that most users won't actually hit,
but it is a 5 line change that fixes four xfstests regressions between v4.3 and
v4.4 for my DAX testing...
Is there a strong reason *not* to push it in the v4.4 cycle? I'm trying to
clear up all xfstests differences between DAX and non-DAX, and this would help
quite a bit.
next prev parent reply other threads:[~2015-12-11 4:26 UTC|newest]
Thread overview: 19+ 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 18:34 ` Ross Zwisler
2015-12-02 20:02 ` Eric Sandeen
2015-12-02 20:10 ` Dan Williams
2015-12-02 20:10 ` Dan Williams
2015-12-02 20:29 ` Dave Chinner
2015-12-02 20:29 ` Dave Chinner
2015-12-02 20:45 ` Dave Chinner
2015-12-02 20:45 ` Dave Chinner
2015-12-02 21:39 ` Ross Zwisler
2015-12-02 21:39 ` Ross Zwisler
2015-12-10 16:54 ` Ross Zwisler
2015-12-10 16:54 ` Ross Zwisler
2015-12-10 22:33 ` Dave Chinner
2015-12-10 22:33 ` Dave Chinner
2015-12-11 4:26 ` Ross Zwisler [this message]
2015-12-11 4:26 ` Ross Zwisler
2015-12-14 0:20 ` Dave Chinner
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=20151211042609.GA5360@linux.intel.com \
--to=ross.zwisler@linux.intel.com \
--cc=bfoster@redhat.com \
--cc=david@fromorbit.com \
--cc=jmoyer@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.