From: Josef Bacik <jbacik@fusionio.com>
To: Stefan Behrens <sbehrens@giantdisaster.de>
Cc: Josef Bacik <jbacik@fusionio.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Btrfs: fail device statistic reset on read-only filesystem
Date: Fri, 11 Oct 2013 10:22:31 -0400 [thread overview]
Message-ID: <20131011142231.GB5095@localhost.localdomain> (raw)
In-Reply-To: <52580629.90307@giantdisaster.de>
On Fri, Oct 11, 2013 at 04:07:37PM +0200, Stefan Behrens wrote:
> On Fri, 11 Oct 2013 09:47:33 -0400, Josef Bacik wrote:
> > Hey look something else that should go into xfstests,
>
> I don't think so. It's a bug that is there from the very beginning, not
> a regression. We can't catch all possible errors (non-regressions) with
> xfstests. We would spend all time for writing xfstests, there wouldn't
> be any time left to actually add bugs.
>
Sure it's been there forever, but now that we've fixed it I'd like to make sure
we don't ever have to fix it again.
Josef
prev parent reply other threads:[~2013-10-11 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 12:18 [PATCH] Btrfs: fail device statistic reset on read-only filesystem Stefan Behrens
2013-10-11 13:47 ` Josef Bacik
2013-10-11 14:07 ` Stefan Behrens
2013-10-11 14:22 ` Josef Bacik [this message]
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=20131011142231.GB5095@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sbehrens@giantdisaster.de \
/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).