public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/2] btrfs-progs: make corrupt-block metadata geneartion corruption work again
Date: Thu, 15 Sep 2022 16:34:32 +0200	[thread overview]
Message-ID: <20220915143432.GP32411@twin.jikos.cz> (raw)
In-Reply-To: <cover.1663053391.git.wqu@suse.com>

On Tue, Sep 13, 2022 at 03:19:24PM +0800, Qu Wenruo wrote:
> This is preparing for the incoming metadata validation refactor in
> kernel, thus I need a way to corrupt transid reliably with correct
> checksum.
> 
> The first patch is to unexport csum_tree_block() which also has a stale
> definition .
> 
> The second patch is to fix the csum for metadata block with corrupted
> generation.
> 
> Now btrfs-corrupt-block can properly corrupt the generation of a tree
> block.
> 
> (But unfortunately it corrupts all copies, which is still not exactly
> what I need, but is already good enough)
> 
> Qu Wenruo (2):
>   btrfs-progs: unexport csum_tree_block()
>   btrfs-progs: corrupt-block: re-generate the checksum for generation
>     corruption

Added to devel, thanks.

      parent reply	other threads:[~2022-09-15 14:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13  7:19 [PATCH 0/2] btrfs-progs: make corrupt-block metadata geneartion corruption work again Qu Wenruo
2022-09-13  7:19 ` [PATCH 1/2] btrfs-progs: unexport csum_tree_block() Qu Wenruo
2022-09-13  7:19 ` [PATCH 2/2] btrfs-progs: corrupt-block: re-generate the checksum for generation corruption Qu Wenruo
2022-09-15 14:34 ` 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=20220915143432.GP32411@twin.jikos.cz \
    --to=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