From: Eric Sandeen <sandeen@sandeen.net>
To: Mark Tinguely <tinguely@sgi.com>, Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: xfstest failures
Date: Thu, 07 Nov 2013 07:58:24 -0600 [thread overview]
Message-ID: <527B9C80.4060304@sandeen.net> (raw)
In-Reply-To: <527B94A5.20004@sgi.com>
On 11/7/13, 7:24 AM, Mark Tinguely wrote:
> On 11/07/13 02:16, Christoph Hellwig wrote:
>> On Wed, Nov 06, 2013 at 01:58:31PM -0600, Mark Tinguely wrote:
>>>
>>>>> xfs/206
>>>>>
>>>>> Does not expect the ftype flag. Didn't we change a generic
>>>>> filter to take care of this?
>>>>
>>>> xfs/206 has it's own mkfs filter:
>>>>
>>>> http://oss.sgi.com/archives/xfs/2013-10/msg00777.html
>>
>> And why is this patch not merged?
>>
>
> It was never reviewed.
Nor was xfstests: filter projid32bit info out of growfs & info output
which I sent originally, before the ftype stuff went in.
Nor was xfstests: New _require_* tests for CRC enabled filesystems which
Dave sent back in June, which Dave alluded to as fixing this as well.
I circled back to it in October w/ a suggestion but haven't seen a
repost.
This lag is clearly causing headaches for all of us; let's just take
a deep breath & get these taken care of.
We had a really high rate of change there for a while, and keeping up on
all fronts was tough.
There's been a bit of defensiveness in the replies here; let's get past
that & take Christoph's list of failures and just get them taken care of.
I'll try to go through the failures and either pick up existing patches,
or get new ones written, and get a new series on the list to get this all
cleaned up.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-11-07 13:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 10:54 xfstest failures Christoph Hellwig
2013-11-06 16:18 ` Ben Myers
2013-11-06 18:20 ` Eric Sandeen
2013-11-07 8:17 ` Christoph Hellwig
2013-11-07 13:24 ` Eric Sandeen
2013-11-07 13:27 ` Christoph Hellwig
2013-11-07 13:46 ` Eric Sandeen
2013-11-07 13:48 ` Christoph Hellwig
2013-11-07 20:49 ` Ben Myers
2013-11-10 20:34 ` Dave Chinner
2013-11-10 20:33 ` Dave Chinner
2013-11-06 19:44 ` Dave Chinner
2013-11-06 19:58 ` Mark Tinguely
2013-11-07 8:16 ` Christoph Hellwig
2013-11-07 13:24 ` Mark Tinguely
2013-11-07 13:58 ` Eric Sandeen [this message]
2013-11-07 14:00 ` Christoph Hellwig
2013-11-07 14:02 ` Eric Sandeen
2013-11-07 20:59 ` Christoph Hellwig
2013-11-07 8:22 ` Christoph Hellwig
2013-11-07 11:57 ` Dave Chinner
2013-11-07 12:01 ` Christoph Hellwig
2013-11-07 12:23 ` Christoph Hellwig
2013-11-07 13:14 ` Markus Trippelsdorf
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=527B9C80.4060304@sandeen.net \
--to=sandeen@sandeen.net \
--cc=hch@infradead.org \
--cc=tinguely@sgi.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