All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: WorMzy Tykashi <wormzy.tykashi@gmail.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs-progs: integration-20141218 possible corruption test regression
Date: Fri, 19 Dec 2014 14:23:12 +0800	[thread overview]
Message-ID: <5493C450.8060204@cn.fujitsu.com> (raw)
In-Reply-To: <719D86DC-BC2F-4A9C-9D17-F90AFFF3FFC2@gmail.com>


-------- Original Message --------
Subject: Re: btrfs-progs: integration-20141218 possible corruption test 
regression
From: WorMzy Tykashi <wormzy.tykashi@gmail.com>
To: <linux-btrfs@vger.kernel.org>
Date: 2014年12月19日 02:39
> On 18 December 2014 18:35:16 GMT+00:00, WorMzy Tykashi <wormzy.tykashi@gmail.com> wrote:
>> Hi guys,
>>
>> The latest integration fails 'make test' with the following output:
>>
>>      [TEST]    013-leaf-corruption-no-extent-data.tar.xz
>> btrfs check should have detected corruption
>> Makefile:144: recipe for target 'test' failed
>> make: *** [test] Error 1
>> rm btrfs-corrupt-block.o
>>
>>
>> I've only built the progs on a single machine so far, but it
>> consistently fails at this test.
>>
>> Cheers,
>>
>>
>> WorMzy
> Regression is present in the 3.18.x branch too.
>
> Cheers,
>
>
> WorMzy
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
In fact, it's not a regression.

The 013 testcase is a special case that uses a script to corrupt the 
image and then do the btrfsck test.

There is a patch before the commit, to allow btrfs-progs test script 
call corruption script.
But since there is still some discussion about the corruption script and 
maybe later verify script,
the previous patch is not picked.

So btrfsck is ran on the *FINE* image without corrupting it, so you 
failed the test.

This testcase seems not to be included into 3.18.x soon, so it's not a 
problem.

If you still want to test it, please add the following patch as a 
temporary fix:
https://patchwork.kernel.org/patch/5490241/

Thanks,
Qu

  reply	other threads:[~2014-12-19  6:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-18 18:35 btrfs-progs: integration-20141218 possible corruption test regression WorMzy Tykashi
2014-12-18 18:39 ` WorMzy Tykashi
2014-12-19  6:23   ` Qu Wenruo [this message]
2014-12-19 13:48     ` David Sterba
2014-12-19 17:00       ` WorMzy Tykashi

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=5493C450.8060204@cn.fujitsu.com \
    --to=quwenruo@cn.fujitsu.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wormzy.tykashi@gmail.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.