From: Tim Landscheidt <tim@tim-landscheidt.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: Don't allocate inode that is already in use
Date: Wed, 16 Oct 2013 17:26:00 +0000 [thread overview]
Message-ID: <87k3hdt9ef.fsf@passepartout.tim-landscheidt.de> (raw)
In-Reply-To: 525E845D.70901@jan-o-sch.net
Jan Schmidt <list.btrfs@jan-o-sch.net> wrote:
> [...]
> You don't quote my second argument, which is not "just skip regression testing".
> I'll try again in other words: A regression test only makes sense if it can
> prevent us from making the same mistake again. As far as I see, the reproducer
> script is so specific, that the only thing it can prevent is an exact revert of
> Stefan's patch. If you argue that we should have a test for just this, fair
> enough, then we could use exactly Stefan's script. I don't think that gains us
> anything. We're not normally reverting bugfix patches deliberately, especially
> not for very short patches with very long descriptions.
> [...]
The presence of the bug in the current code indicates that
someone in the past made an error, and that suggests that
this error can be repeated (by someone else) for example in
a rewrite months or years in the future. The purpose of a
regression test is to spare anyone who touches the code to
go through all the commits to see if they're unintentionally
reverting a bug fix, but give them a nice "FAIL"/"PASS"
traffic light.
Tim
prev parent reply other threads:[~2013-10-16 18:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 18:08 [PATCH] Btrfs: Don't allocate inode that is already in use Stefan Behrens
2013-10-15 18:54 ` Jan Schmidt
2013-10-15 20:41 ` Zach Brown
2013-10-16 12:19 ` Jan Schmidt
2013-10-16 16:46 ` Zach Brown
2013-10-16 17:26 ` Tim Landscheidt [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=87k3hdt9ef.fsf@passepartout.tim-landscheidt.de \
--to=tim@tim-landscheidt.de \
--cc=linux-btrfs@vger.kernel.org \
/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