public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Josef Bacik <josef@toxicpanda.com>
Cc: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH 0/7] btrfs-progs: various regression fixes
Date: Tue, 8 Mar 2022 18:39:04 +0100	[thread overview]
Message-ID: <20220308173903.GR12643@twin.jikos.cz> (raw)
In-Reply-To: <cover.1645567860.git.josef@toxicpanda.com>

On Tue, Feb 22, 2022 at 05:22:35PM -0500, Josef Bacik wrote:
> Hello,
> 
> In trying to test my new extent tree v2 patches I noticed I had regressed a few
> of these tests with my previous prep patches.  I'm not entirely sure how I
> missed this before as I generally run the tests, but there are some clear things
> that need fixing.  I've based these patches on the devel branch, with them in
> place everything passes as it should.  Thanks,
> 
> Josef
> 
> Josef Bacik (7):
>   btrfs-progs: check: fix check_global_roots_uptodate
>   btrfs-progs: fuzz-tests: use --force for --init-csum-tree
>   btrfs-progs: repair: bail if we find an unaligned extent
>   btrfs-progs: properly populate missing trees
>   btrfs-progs: don't check skip_csum_check if there's no fs_info
>   btrfs-progs: do not try to load the free space tree if it's not
>     enabled
>   btrfs-progs: inspect-tree-stats: initialize the key properly

Added to devel, thanks.

      parent reply	other threads:[~2022-03-08 17:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-22 22:22 [PATCH 0/7] btrfs-progs: various regression fixes Josef Bacik
2022-02-22 22:22 ` [PATCH 1/7] btrfs-progs: check: fix check_global_roots_uptodate Josef Bacik
2022-03-08 17:16   ` David Sterba
2022-02-22 22:22 ` [PATCH 2/7] btrfs-progs: fuzz-tests: use --force for --init-csum-tree Josef Bacik
2022-02-22 22:22 ` [PATCH 3/7] btrfs-progs: repair: bail if we find an unaligned extent Josef Bacik
2022-02-22 22:22 ` [PATCH 4/7] btrfs-progs: properly populate missing trees Josef Bacik
2022-03-04 22:18   ` David Sterba
2022-03-08 17:26     ` David Sterba
2022-02-22 22:22 ` [PATCH 5/7] btrfs-progs: don't check skip_csum_check if there's no fs_info Josef Bacik
2022-02-22 22:22 ` [PATCH 6/7] btrfs-progs: do not try to load the free space tree if it's not enabled Josef Bacik
2022-02-22 22:22 ` [PATCH 7/7] btrfs-progs: inspect-tree-stats: initialize the key properly Josef Bacik
2022-03-08 17:39 ` David Sterba [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=20220308173903.GR12643@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=josef@toxicpanda.com \
    --cc=kernel-team@fb.com \
    --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