From: Christoph Hellwig <hch@lst.de>
To: Nikolay Borisov <nborisov@suse.com>
Cc: Christoph Hellwig <hch@lst.de>, Chris Mason <clm@fb.com>,
Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 4/4] btrfs: fix repair of compressed extents
Date: Thu, 7 Jul 2022 15:30:08 +0200 [thread overview]
Message-ID: <20220707133008.GA18415@lst.de> (raw)
In-Reply-To: <f8773669-79a7-6cbc-4c70-b805527b3268@suse.com>
On Thu, Jul 07, 2022 at 03:50:34PM +0300, Nikolay Borisov wrote:
>> + btrfs_bio_for_each_sector(fs_info, bv, bbio, iter, offset) {
>> + u64 start = bbio->file_offset + offset;
>> +
>> + if (!status &&
>> + (!csum || !check_data_csum(inode, bbio, offset, bv.bv_page,
>> + bv.bv_offset))) {
>
> In the !csum case you'd be executing a lot of code for no gain i.e
> clean_io_failure. Instead, factor out the !csum case as a break from the
> btrfs_bio_for_each_sector i.e no point in running clean_io_failure for
> every sector in this case.
We still need to call clean_io_failure in that case, as repair can
also happen when I/O failed even without checksums. Note that this
code also is just a copy and paste from the direct I/O completion
handler, and an equivalent but more obsfucated version of same
logic also exists in the buffered I/O completion path.
(and before anyone asks, I do have a WIP patchset to consolidate the
logic, and remove the calls to clean_io_failure for non-repair bio
completions, but it will take a while to get there).
>> - cb = kmalloc(compressed_bio_size(fs_info, compressed_len), GFP_NOFS);
>> + cb = kmalloc(sizeof(struct compressed_bio), GFP_NOFS);
>
> nit: This change is irrelevant to this patch - indeed we don't need to
> allocate the flex array at the end of compressed_bio for writes, as the
> csums are being stored in the ordered extents for the bio, still this it's
> independent of this patch.
True.
next prev parent reply other threads:[~2022-07-07 13:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 16:01 fix read repair on compressed extents v2 Christoph Hellwig
2022-06-30 16:01 ` [PATCH 1/4] btrfs: simplify the pending I/O counting in struct compressed_bio Christoph Hellwig
2022-07-05 14:40 ` Nikolay Borisov
2022-07-05 17:17 ` Christoph Hellwig
2022-06-30 16:01 ` [PATCH 2/4] btrfs: pass a btrfs_bio to btrfs_repair_one_sector Christoph Hellwig
2022-06-30 16:01 ` [PATCH 3/4] btrfs: remove the start argument to check_data_csum Christoph Hellwig
2022-07-05 15:35 ` Nikolay Borisov
2022-07-05 17:18 ` Christoph Hellwig
2022-06-30 16:01 ` [PATCH 4/4] btrfs: fix repair of compressed extents Christoph Hellwig
2022-07-07 12:50 ` Nikolay Borisov
2022-07-07 13:30 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-23 5:53 fix read repair on " Christoph Hellwig
2022-06-23 5:53 ` [PATCH 4/4] btrfs: fix repair of " Christoph Hellwig
2022-06-30 0:18 ` Boris Burkov
2022-06-30 4:24 ` Christoph Hellwig
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=20220707133008.GA18415@lst.de \
--to=hch@lst.de \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@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 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.