public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: dsterba@suse.cz, Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/6] btrfs-progs: Fixes for github issues
Date: Fri, 3 Jan 2020 08:43:01 +0800	[thread overview]
Message-ID: <e8398282-264a-3ef7-43d5-63f1ac0c7c19@gmx.com> (raw)
In-Reply-To: <20200102171056.GM3929@twin.jikos.cz>


[-- Attachment #1.1: Type: text/plain, Size: 1452 bytes --]



On 2020/1/3 上午1:10, David Sterba wrote:
> On Wed, Dec 18, 2019 at 09:19:36AM +0800, Qu Wenruo wrote:
>> There are a new batch of fuzzed images for btrfs-progs. They are all
>> reported by Ruud van Asseldonk from github.
>>
>> Patch 1 will make QA life easier by remove the extra 300s wait time.
>> Patch 2~5 are all the meat for the fuzzed images.
>>
>> Just a kind reminder, mkfs/020 test will fail due to tons of problems:
>> - Undefined $csum variable
>> - Undefined $dev1 variable
> 
> These are fixed in devel now.
> 
>> - Bad kernel probe for support csum
>>   E.g. if Blake2 not compiled, it still shows up in supported csum algo,
>>   but will fail to mount.
> 
> The list of supported is from the point of view of the filesystem.
> Providing the module is up to the user.

IIRC, doing such probe at btrfs module load time would be more user
friendly though.

Thanks,
Qu

> 
>> All other tests pass.
>>
>> Qu Wenruo (6):
>>   btrfs-progs: tests: Add --force for repair command
>>   btrfs-progs: check/original: Do extra verification on file extent item
>>   btrfs-progs: disk-io: Verify the bytenr passed in is mapped for
>>     read_tree_block()
>>   btrfs-progs: Add extra chunk item size check
>>   btrfs-progs: extent-tree: Kill the BUG_ON() in btrfs_chunk_readonly()
>>   btrfs-progs: extent-tree: Fix a by-one error in
>>     exclude_super_stripes()
> 
> All added to devel, thanks.
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 520 bytes --]

  reply	other threads:[~2020-01-03  0:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-18  1:19 [PATCH 0/6] btrfs-progs: Fixes for github issues Qu Wenruo
2019-12-18  1:19 ` [PATCH 1/6] btrfs-progs: tests: Add --force for repair command Qu Wenruo
2019-12-18  1:19 ` [PATCH 2/6] btrfs-progs: check/original: Do extra verification on file extent item Qu Wenruo
2019-12-18  2:09   ` Su Yue
2019-12-18  2:17     ` Qu Wenruo
2019-12-18  2:19       ` Su Yue
2019-12-18  1:19 ` [PATCH 3/6] btrfs-progs: disk-io: Verify the bytenr passed in is mapped for read_tree_block() Qu Wenruo
2019-12-18  1:19 ` [PATCH 4/6] btrfs-progs: Add extra chunk item size check Qu Wenruo
2019-12-18  1:19 ` [PATCH 5/6] btrfs-progs: extent-tree: Kill the BUG_ON() in btrfs_chunk_readonly() Qu Wenruo
2019-12-18  1:19 ` [PATCH 6/6] btrfs-progs: extent-tree: Fix a by-one error in exclude_super_stripes() Qu Wenruo
2020-01-02 16:56   ` David Sterba
2020-01-03  0:42     ` Qu Wenruo
2020-01-03  3:04       ` Su Yue
2020-01-02 17:10 ` [PATCH 0/6] btrfs-progs: Fixes for github issues David Sterba
2020-01-03  0:43   ` Qu Wenruo [this message]
2020-01-03 15:27     ` David Sterba
2020-01-04  1:26       ` Qu Wenruo
2020-01-06 15:45         ` David Sterba
2020-01-07  1:46           ` Qu Wenruo

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=e8398282-264a-3ef7-43d5-63f1ac0c7c19@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wqu@suse.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