From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v3 1/4] btrfs: remove the dead branch in btrfs_io_needs_validation()
Date: Mon, 3 May 2021 19:05:04 +0200 [thread overview]
Message-ID: <20210503170504.GN7604@twin.jikos.cz> (raw)
In-Reply-To: <20210503020856.93333-2-wqu@suse.com>
On Mon, May 03, 2021 at 10:08:53AM +0800, Qu Wenruo wrote:
> In function btrfs_io_needs_validation() we are ensured to get a
> non-cloned bio.
> The only caller, end_bio_extent_readpage(), already has an ASSERT() to
> make sure we only get non-cloned bios.
>
> Thus the (bio_flagged(bio, BIO_CLONED)) branch will never get executed.
>
> Remove the dead branch and updated the comment.
>
> Signed-off-by: Qu Wenruo <wqu@suse.com>
> ---
> fs/btrfs/extent_io.c | 29 +++++++----------------------
> 1 file changed, 7 insertions(+), 22 deletions(-)
>
> diff --git a/fs/btrfs/extent_io.c b/fs/btrfs/extent_io.c
> index 14ab11381d49..0787fae5f7f1 100644
> --- a/fs/btrfs/extent_io.c
> +++ b/fs/btrfs/extent_io.c
> @@ -2644,8 +2644,10 @@ static bool btrfs_check_repairable(struct inode *inode, bool needs_validation,
>
> static bool btrfs_io_needs_validation(struct inode *inode, struct bio *bio)
> {
> + struct bio_vec *bvec;
> u64 len = 0;
> const u32 blocksize = inode->i_sb->s_blocksize;
> + int i;
>
> /*
> * If bi_status is BLK_STS_OK, then this was a checksum error, not an
> @@ -2669,30 +2671,13 @@ static bool btrfs_io_needs_validation(struct inode *inode, struct bio *bio)
> if (blocksize < PAGE_SIZE)
> return false;
> /*
> - * We need to validate each sector individually if the failed I/O was
> - * for multiple sectors.
> - *
> - * There are a few possible bios that can end up here:
> - * 1. A buffered read bio, which is not cloned.
> - * 2. A direct I/O read bio, which is cloned.
Ok, so the cloned bio was expected only due to direct io but now it's
done via iomap so it makes sense to simplify it.
> - * 3. A (buffered or direct) repair bio, which is not cloned.
> - *
> - * For cloned bios (case 2), we can get the size from
> - * btrfs_io_bio->iter; for non-cloned bios (cases 1 and 3), we can get
> - * it from the bvecs.
> + * We're ensured we won't get cloned bio in end_bio_extent_readpage(),
> + * thus we can get the length from the bvecs.
> */
> - if (bio_flagged(bio, BIO_CLONED)) {
> - if (btrfs_io_bio(bio)->iter.bi_size > blocksize)
> + bio_for_each_bvec_all(bvec, bio, i) {
> + len += bvec->bv_len;
> + if (len > blocksize)
> return true;
> - } else {
> - struct bio_vec *bvec;
> - int i;
> -
> - bio_for_each_bvec_all(bvec, bio, i) {
> - len += bvec->bv_len;
> - if (len > blocksize)
> - return true;
> - }
> }
> return false;
> }
> --
> 2.31.1
next prev parent reply other threads:[~2021-05-03 17:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 2:08 [PATCH v3 0/4] btrfs: make read time repair to be only submitted for each corrupted sector Qu Wenruo
2021-05-03 2:08 ` [PATCH v3 1/4] btrfs: remove the dead branch in btrfs_io_needs_validation() Qu Wenruo
2021-05-03 17:05 ` David Sterba [this message]
2021-05-03 23:39 ` Qu Wenruo
2021-05-10 20:14 ` David Sterba
2021-05-10 23:56 ` Qu Wenruo
2021-05-11 11:27 ` David Sterba
2021-05-03 2:08 ` [PATCH v3 2/4] btrfs: make btrfs_verify_data_csum() to return a bitmap Qu Wenruo
2021-05-03 2:08 ` [PATCH v3 3/4] btrfs: submit read time repair only for each corrupted sector Qu Wenruo
2021-05-10 20:32 ` David Sterba
2021-05-11 1:42 ` Qu Wenruo
2021-05-11 11:35 ` David Sterba
2021-05-03 2:08 ` [PATCH v3 4/4] btrfs: remove io_failure_record::in_validation Qu Wenruo
2021-05-10 20:41 ` [PATCH v3 0/4] btrfs: make read time repair to be only submitted for each corrupted sector David Sterba
2021-05-11 1:07 ` Qu Wenruo
2021-05-11 11:59 ` David Sterba
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=20210503170504.GN7604@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