All of lore.kernel.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: csum failure messages
Date: Wed, 6 Nov 2013 12:19:54 +0000 (UTC)	[thread overview]
Message-ID: <pan$a6cc3$5081ede9$fee68bf7$e93d0c29@cox.net> (raw)
In-Reply-To: CAJBj3veWmB4m+pR2SdZ=y4pRVXfR5aGpfjH2HhoFXbARcZy34w@mail.gmail.com

John Williams posted on Tue, 05 Nov 2013 16:20:58 -0800 as excerpted:

> Is there now a verification test that could detect an issue like this?
> It seems like the sort of thing that needs to be added to automated
> testing.

[Your question is general enough, not mentioning xfs-tests, simply asking 
about general automated testing, I'm assuming a general answer is 
appropriate.]

I haven't tracked this specific issue, but in general, the btrfs devs are 
pretty strict with adding an xfs-tests (NOT used for just xfs, at least 
btrfs and ext4 use it too) package test for any regressions they find, 
and people ARE regularly running those tests on new code, so past issues 
don't happen again.  

If you watch the list you'll see occasional patch rejections due to 
failed xfs-tests, as well as regular new xfs-tests patches adding new 
tests, as well as review discussion requesting an xfs-test be added as 
appropriate.

So I'd be /very/ surprised if this bugfix didn't already have a 
corresponding new xfs-tests test.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2013-11-06 12:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05  1:24 csum failure messages Russell Coker
2013-11-05  6:15 ` Hans-Kristian Bakke
2013-11-05 11:30   ` David Sterba
2013-11-05 12:16   ` Russell Coker
2013-11-05 12:37     ` Hans-Kristian Bakke
2013-11-05 14:26     ` Chris Murphy
2013-11-05 14:34       ` Hugo Mills
2013-11-06  0:20         ` John Williams
2013-11-06 12:19           ` Duncan [this message]
2013-11-06 16:54           ` David Sterba
2013-11-14 18:37         ` Chris Murphy
2013-11-14 18:44           ` David Sterba

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='pan$a6cc3$5081ede9$fee68bf7$e93d0c29@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --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 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.