public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
	David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: fix read repair on compressed extents
Date: Wed, 29 Jun 2022 10:42:01 +0200	[thread overview]
Message-ID: <20220629084201.GA25725@lst.de> (raw)
In-Reply-To: <20220623055338.3833616-1-hch@lst.de>

Any chance to get a review on this one?

On Thu, Jun 23, 2022 at 07:53:34AM +0200, Christoph Hellwig wrote:
> Hi all,
> 
> while looking into the repair code I found that read repair of compressed
> extents is current fundamentally broken, in that repair tries to write
> the uncompressed data into a corrupted extent during a repair.  This is
> demonstrated by the "btrfs: test read repair on a corrupted compressed
> extent" test submitted to xfstests.
> 
> This series fixes that, but is a bit invaside as it requires both
> refactoring of the compression code and changes to the repair code to
> not look up the logic address on every repair attempt.  On the plus
> side it removes a whole lot of code.
> 
> It is based on the for-next branch plus my "btrfs: repair all known bad
> mirrors" patch.
> 
> Diffstat:
>  compression.c |  287 ++++++++++++++++------------------------------------------
>  compression.h |   11 --
>  ctree.h       |    4 
>  extent_io.c   |   93 +++++++-----------
>  extent_io.h   |    9 -
>  inode.c       |   34 +++---
>  6 files changed, 148 insertions(+), 290 deletions(-)
---end quoted text---

  parent reply	other threads:[~2022-06-29  8:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-23  5:53 fix read repair on compressed extents Christoph Hellwig
2022-06-23  5:53 ` [PATCH 1/4] btrfs: simplify the pending I/O counting in struct compressed_bio Christoph Hellwig
2022-06-29 23:42   ` Boris Burkov
2022-06-30  4:22     ` Christoph Hellwig
2022-06-23  5:53 ` [PATCH 2/4] btrfs: pass a btrfs_bio to btrfs_repair_one_sector Christoph Hellwig
2022-06-29 23:44   ` Boris Burkov
2022-06-30  4:23     ` Christoph Hellwig
2022-06-23  5:53 ` [PATCH 3/4] btrfs: remove the start argument to check_data_csum Christoph Hellwig
2022-06-29 23:48   ` Boris Burkov
2022-06-23  5:53 ` [PATCH 4/4] btrfs: fix repair of compressed extents Christoph Hellwig
2022-06-30  0:18   ` Boris Burkov
2022-06-30  4:24     ` Christoph Hellwig
2022-06-23  8:14 ` fix read repair on " Qu Wenruo
2022-06-23 12:58   ` Christoph Hellwig
2022-06-29  8:42 ` Christoph Hellwig [this message]
2022-06-29 19:04   ` Boris Burkov
2022-06-29 19:08     ` Christoph Hellwig
2022-06-29 19:38       ` Boris Burkov

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=20220629084201.GA25725@lst.de \
    --to=hch@lst.de \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=josef@toxicpanda.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