From: Nikolay Borisov <nborisov@suse.com>
To: Omar Sandoval <osandov@osandov.com>, linux-btrfs@vger.kernel.org
Cc: kernel-team@fb.com, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 15/15] btrfs: unify buffered and direct I/O read repair
Date: Thu, 19 Mar 2020 10:53:22 +0200 [thread overview]
Message-ID: <37bf11cc-92b3-2b15-ee87-0cbe8c662cc7@suse.com> (raw)
In-Reply-To: <7c593decda73deb58515d94e979db6a68527970b.1583789410.git.osandov@fb.com>
On 9.03.20 г. 23:32 ч., Omar Sandoval wrote:
> From: Omar Sandoval <osandov@fb.com>
>
> Currently, direct I/O has its own versions of bio_readpage_error() and
> btrfs_check_repairable() (dio_read_error() and
> btrfs_check_dio_repairable(), respectively). The main difference is that
> the direct I/O version doesn't do read validation. The rework of direct
> I/O repair makes it possible to do validation, so we can get rid of
> btrfs_check_dio_repairable() and combine bio_readpage_error() and
> dio_read_error() into a new helper, btrfs_submit_read_repair().
>
> Signed-off-by: Omar Sandoval <osandov@fb.com>
> ---
> fs/btrfs/extent_io.c | 126 +++++++++++++++++++------------------------
> fs/btrfs/extent_io.h | 17 +++---
> fs/btrfs/inode.c | 103 ++++-------------------------------
> 3 files changed, 76 insertions(+), 170 deletions(-)
>
> diff --git a/fs/btrfs/extent_io.c b/fs/btrfs/extent_io.c
> index fad86ef4d09d..a5cbe04da803 100644
> --- a/fs/btrfs/extent_io.c
> +++ b/fs/btrfs/extent_io.c
<snip>
> -/*
> - * This is a generic handler for readpage errors. If other copies exist, read
> - * those and write back good data to the failed position. Does not investigate
> - * in remapping the failed extent elsewhere, hoping the device will be smart
> - * enough to do this as needed
> - */
> -static int bio_readpage_error(struct bio *failed_bio, u64 phy_offset,
> - struct page *page, u64 start, u64 end,
> - int failed_mirror)
> +blk_status_t btrfs_submit_read_repair(struct inode *inode,
> + struct bio *failed_bio, u64 phy_offset,
> + struct page *page, unsigned int pgoff,
> + u64 start, u64 end, int failed_mirror,
> + submit_bio_hook_t *submit_bio_hook)
> {
> struct io_failure_record *failrec;
> - struct inode *inode = page->mapping->host;
> + struct btrfs_fs_info *fs_info = btrfs_sb(inode->i_sb);
> struct extent_io_tree *tree = &BTRFS_I(inode)->io_tree;
> struct extent_io_tree *failure_tree = &BTRFS_I(inode)->io_failure_tree;
> + struct btrfs_io_bio *failed_io_bio = btrfs_io_bio(failed_bio);
> + struct btrfs_io_bio *io_bio;
> + int icsum = phy_offset >> inode->i_sb->s_blocksize_bits;
> bool need_validation = false;
> struct bio *bio;
> - int read_mode = 0;
> blk_status_t status;
> int ret;
>
> + btrfs_info(btrfs_sb(inode->i_sb),
> + "Repair Read Error: read error at %llu", start);
> +
> BUG_ON(bio_op(failed_bio) == REQ_OP_WRITE);
>
> ret = btrfs_get_io_failure_record(inode, start, end, &failrec);
> if (ret)
> - return ret;
> + return errno_to_blk_status(ret);
>
> /*
> * If there was an I/O error and the I/O was for multiple sectors, we
> * need to validate each sector individually.
> */
> if (failed_bio->bi_status != BLK_STS_OK) {
Is this correct though, in case of buffered reads we are always called
with bi_status != BLK_STS_OK (we are called from end_bio_extent_readpage
in case uptodate is false, which happens if failed_bio->bi_status is
non-zero. Additionally the bio is guaranteed to not be cloned because
there is : ASSERT(!bio_flagged(bio, BIO_CLONED));
The end effect of all of this is in case of buffered bios we never set
need_revalidate, is this intentional?
> - u64 len = 0;
> - int i;
> -
> - for (i = 0; i < failed_bio->bi_vcnt; i++) {
> - len += failed_bio->bi_io_vec[i].bv_len;
> - if (len > inode->i_sb->s_blocksize) {
> + if (bio_flagged(failed_bio, BIO_CLONED)) {
If I understand this correctly this is the "this is a DIO " branch. IMO
it'd be clearer if you had bool is_dio = bio_flagged(failed_bio,
BIO_CLONED) at the top of the function and you used that.
> + if (failed_io_bio->iter.bi_size >
> + inode->i_sb->s_blocksize)
> need_validation = true;
> - break;
> + } else {
This branch will only ever be executed in case of DIO with csum failure.
So either add a comment to demarcate when various leaves of the 2 'if'
should be called or, and I think this would be the better solution,
rewrite it.
> + u64 len = 0;
> + int i;
> +
> + for (i = 0; i < failed_bio->bi_vcnt; i++) {
> + len += failed_bio->bi_io_vec[i].bv_len;
> + if (len > inode->i_sb->s_blocksize) {
> + need_validation = true;
> + break;
> + }
> }
> }
> }
> @@ -2674,32 +2646,41 @@ static int bio_readpage_error(struct bio *failed_bio, u64 phy_offset,
> if (!btrfs_check_repairable(inode, need_validation, failrec,
> failed_mirror)) {
> free_io_failure(failure_tree, tree, failrec);
> - return -EIO;
> + return BLK_STS_IOERR;
> }
>
> + bio = btrfs_io_bio_alloc(1);
> + io_bio = btrfs_io_bio(bio);
> + bio->bi_opf = REQ_OP_READ;
> if (need_validation)
> - read_mode |= REQ_FAILFAST_DEV;
> + bio->bi_opf |= REQ_FAILFAST_DEV;
> + bio->bi_end_io = failed_bio->bi_end_io;
> + bio->bi_iter.bi_sector = failrec->logical >> 9;
> + bio->bi_private = failed_bio->bi_private;
nit: I'd rather have this named as repair_bio, right now the function has:
failed_bio, failed_io_bio and simply bio. But in fact the latter is a
repair bio derived from the io_failured_record.
>
> - phy_offset >>= inode->i_sb->s_blocksize_bits;
> - bio = btrfs_create_repair_bio(inode, failed_bio, failrec, page,
> - start - page_offset(page),
> - (int)phy_offset, failed_bio->bi_end_io,
> - NULL);
> - bio->bi_opf = REQ_OP_READ | read_mode;
> + if (failed_io_bio->csum) {
> + u16 csum_size = btrfs_super_csum_size(fs_info->super_copy);
> +
> + io_bio->csum = io_bio->csum_inline;
> + memcpy(io_bio->csum, failed_io_bio->csum + csum_size * icsum,
> + csum_size);
> + }
> +
> + bio_add_page(bio, page, failrec->len, pgoff);
> + io_bio->logical = failrec->start;
> + io_bio->iter = bio->bi_iter;
>
> btrfs_debug(btrfs_sb(inode->i_sb),
> - "Repair Read Error: submitting new read[%#x] to this_mirror=%d, in_validation=%d",
> - read_mode, failrec->this_mirror, failrec->in_validation);
> +"Repair Read Error: submitting new read to this_mirror=%d, in_validation=%d",
> + failrec->this_mirror, failrec->in_validation);
>
> - status = tree->ops->submit_bio_hook(tree->private_data, bio, failrec->this_mirror,
> - failrec->bio_flags);
> + status = submit_bio_hook(inode, bio, failrec->this_mirror,
> + failrec->bio_flags);
> if (status) {
> free_io_failure(failure_tree, tree, failrec);
> bio_put(bio);
> - ret = blk_status_to_errno(status);
> }
> -
> - return ret;
> + return status;
> }
>
> /* lots and lots of room for performance fixes in the end_bio funcs */
<snip>
>
next prev parent reply other threads:[~2020-03-19 8:53 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 21:32 [PATCH 00/15] btrfs: read repair/direct I/O improvements Omar Sandoval
2020-03-09 21:32 ` [PATCH 01/15] btrfs: fix error handling when submitting direct I/O bio Omar Sandoval
2020-03-11 17:54 ` Josef Bacik
2020-03-17 13:46 ` Nikolay Borisov
2020-03-09 21:32 ` [PATCH 02/15] btrfs: fix double __endio_write_update_ordered in direct I/O Omar Sandoval
2020-03-10 16:30 ` Christoph Hellwig
2020-03-11 9:03 ` Omar Sandoval
2020-03-17 14:04 ` Nikolay Borisov
2020-03-09 21:32 ` [PATCH 03/15] btrfs: look at full bi_io_vec for repair decision Omar Sandoval
2020-03-10 16:33 ` Christoph Hellwig
2020-03-11 9:07 ` Omar Sandoval
2020-03-16 10:48 ` Christoph Hellwig
2020-03-17 14:38 ` Nikolay Borisov
2020-03-09 21:32 ` [PATCH 04/15] btrfs: don't do repair validation for checksum errors Omar Sandoval
2020-03-11 17:55 ` Josef Bacik
2020-03-09 21:32 ` [PATCH 05/15] btrfs: clarify btrfs_lookup_bio_sums documentation Omar Sandoval
2020-03-11 17:56 ` Josef Bacik
2020-03-11 18:23 ` Omar Sandoval
2020-03-11 18:34 ` Josef Bacik
2020-03-17 14:38 ` Nikolay Borisov
2020-03-09 21:32 ` [PATCH 06/15] btrfs: rename __readpage_endio_check to check_data_csum Omar Sandoval
2020-03-10 14:46 ` Johannes Thumshirn
2020-03-11 17:57 ` Josef Bacik
2020-03-17 14:39 ` Nikolay Borisov
2020-03-09 21:32 ` [PATCH 07/15] btrfs: make btrfs_check_repairable() static Omar Sandoval
2020-03-10 14:53 ` Johannes Thumshirn
2020-03-11 17:58 ` Josef Bacik
2020-03-17 14:52 ` Nikolay Borisov
2020-03-09 21:32 ` [PATCH 08/15] btrfs: move btrfs_dio_private to inode.c Omar Sandoval
2020-03-10 14:56 ` Johannes Thumshirn
2020-03-11 8:48 ` Omar Sandoval
2020-03-17 14:53 ` Nikolay Borisov
2020-03-19 16:16 ` David Sterba
2020-03-09 21:32 ` [PATCH 09/15] btrfs: kill btrfs_dio_private->private Omar Sandoval
2020-03-11 17:59 ` Josef Bacik
2020-03-17 14:54 ` Nikolay Borisov
2020-03-09 21:32 ` [PATCH 10/15] btrfs: convert btrfs_dio_private->pending_bios to refcount_t Omar Sandoval
2020-03-11 18:00 ` Josef Bacik
2020-03-17 15:10 ` Nikolay Borisov
2020-03-09 21:32 ` [PATCH 11/15] btrfs: put direct I/O checksums in btrfs_dio_private instead of bio Omar Sandoval
2020-03-11 18:04 ` Josef Bacik
2020-03-17 16:37 ` Nikolay Borisov
2020-04-03 16:18 ` David Sterba
2020-03-09 21:32 ` [PATCH 12/15] btrfs: get rid of one layer of bios in direct I/O Omar Sandoval
2020-03-10 16:38 ` Christoph Hellwig
2020-03-11 9:19 ` Omar Sandoval
2020-03-16 10:49 ` Christoph Hellwig
2020-03-11 18:07 ` Josef Bacik
2020-03-17 16:48 ` Nikolay Borisov
2020-03-09 21:32 ` [PATCH 13/15] btrfs: simplify direct I/O read repair Omar Sandoval
2020-03-11 18:16 ` Josef Bacik
2020-04-03 16:40 ` David Sterba
2020-04-03 18:05 ` Omar Sandoval
2020-04-16 10:08 ` David Sterba
2020-03-09 21:32 ` [PATCH 14/15] btrfs: get rid of endio_repair_workers Omar Sandoval
2020-03-11 18:16 ` Josef Bacik
2020-03-09 21:32 ` [PATCH 15/15] btrfs: unify buffered and direct I/O read repair Omar Sandoval
2020-03-11 18:19 ` Josef Bacik
2020-03-19 8:53 ` Nikolay Borisov [this message]
2020-03-19 9:03 ` Christoph Hellwig
2020-03-20 21:28 ` Omar Sandoval
2020-03-10 16:39 ` [PATCH 00/15] btrfs: read repair/direct I/O improvements Christoph Hellwig
2020-03-11 9:22 ` Omar Sandoval
2020-03-18 16:33 ` Goldwyn Rodrigues
2020-03-19 14:08 ` David Sterba
2020-03-18 22:07 ` David Sterba
2020-03-20 21:29 ` Omar Sandoval
2020-03-20 14:10 ` Christoph Hellwig
2020-03-20 14:11 ` 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=37bf11cc-92b3-2b15-ee87-0cbe8c662cc7@suse.com \
--to=nborisov@suse.com \
--cc=hch@lst.de \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=osandov@osandov.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;
as well as URLs for NNTP newsgroup(s).