From: Boris Burkov <boris@bur.io>
To: Josef Bacik <josef@toxicpanda.com>
Cc: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH 6/8] btrfs: do not double complete bio on errors during compressed reads
Date: Fri, 11 Feb 2022 14:54:22 -0800 [thread overview]
Message-ID: <YgbpHjBvf49gtEbC@zen> (raw)
In-Reply-To: <800ebbe66b4998ec1ac7122cc201c4404d737f18.1644532798.git.josef@toxicpanda.com>
On Thu, Feb 10, 2022 at 05:44:24PM -0500, Josef Bacik wrote:
> I hit some weird panics while fixing up the error handling from
> btrfs_lookup_bio_sums(). Turns out the compression path will complete
> the bio we use if we set up any of the compression bios and then return
> an error, and then btrfs_submit_data_bio() will also call bio_endio() on
> the bio.
>
> Fix this by making btrfs_submit_compressed_read() responsible for
> calling bio_endio() on the bio if there are any errors. Currently it
> was only doing it if we created the compression bios, otherwise it was
> depending on btrfs_submit_data_bio() to do the right thing. This
> creates the above problem, so fix up btrfs_submit_compressed_read() to
> always call bio_endio() in case of an error, and then simply return from
> btrfs_submit_data_bio() if we had to call
> btrfs_submit_compressed_read().
>
> Signed-off-by: Josef Bacik <josef@toxicpanda.com>
Reviewed-by: Boris Burkov <boris@bur.io>
> ---
> fs/btrfs/compression.c | 14 +++++++++-----
> fs/btrfs/inode.c | 12 ++++++++----
> 2 files changed, 17 insertions(+), 9 deletions(-)
>
> diff --git a/fs/btrfs/compression.c b/fs/btrfs/compression.c
> index ee1c6f870a03..9551658ac3a1 100644
> --- a/fs/btrfs/compression.c
> +++ b/fs/btrfs/compression.c
> @@ -808,7 +808,7 @@ blk_status_t btrfs_submit_compressed_read(struct inode *inode, struct bio *bio,
> u64 em_len;
> u64 em_start;
> struct extent_map *em;
> - blk_status_t ret = BLK_STS_RESOURCE;
> + blk_status_t ret;
> int faili = 0;
> u8 *sums;
>
> @@ -821,9 +821,12 @@ blk_status_t btrfs_submit_compressed_read(struct inode *inode, struct bio *bio,
> read_lock(&em_tree->lock);
> em = lookup_extent_mapping(em_tree, file_offset, fs_info->sectorsize);
> read_unlock(&em_tree->lock);
> - if (!em)
> - return BLK_STS_IOERR;
> + if (!em) {
> + ret = BLK_STS_IOERR;
> + goto out;
> + }
>
> + ret = BLK_STS_RESOURCE;
I think the error handling logic with all the special exit paths makes
it worthwhile to set ret at each individual 'goto failX'.
> ASSERT(em->compress_type != BTRFS_COMPRESS_NONE);
> compressed_len = em->block_len;
> cb = kmalloc(compressed_bio_size(fs_info, compressed_len), GFP_NOFS);
> @@ -858,7 +861,6 @@ blk_status_t btrfs_submit_compressed_read(struct inode *inode, struct bio *bio,
> cb->compressed_pages[pg_index] = alloc_page(GFP_NOFS);
> if (!cb->compressed_pages[pg_index]) {
> faili = pg_index - 1;
> - ret = BLK_STS_RESOURCE;
> goto fail2;
> }
> }
> @@ -938,7 +940,7 @@ blk_status_t btrfs_submit_compressed_read(struct inode *inode, struct bio *bio,
> comp_bio = NULL;
> }
> }
> - return 0;
> + return BLK_STS_OK;
>
> fail2:
> while (faili >= 0) {
> @@ -951,6 +953,8 @@ blk_status_t btrfs_submit_compressed_read(struct inode *inode, struct bio *bio,
> kfree(cb);
> out:
> free_extent_map(em);
> + bio->bi_status = ret;
> + bio_endio(bio);
> return ret;
> finish_cb:
> if (comp_bio) {
> diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
> index 24099fe9e120..69fa71186e72 100644
> --- a/fs/btrfs/inode.c
> +++ b/fs/btrfs/inode.c
> @@ -2542,10 +2542,14 @@ blk_status_t btrfs_submit_data_bio(struct inode *inode, struct bio *bio,
> goto out;
>
> if (bio_flags & EXTENT_BIO_COMPRESSED) {
> - ret = btrfs_submit_compressed_read(inode, bio,
> - mirror_num,
> - bio_flags);
> - goto out;
> + /*
> + * btrfs_submit_compressed_read will handle completing
> + * the bio if there were any errors, so just return
> + * here.
> + */
> + return btrfs_submit_compressed_read(inode, bio,
> + mirror_num,
> + bio_flags);
> } else {
> /*
> * Lookup bio sums does extra checks around whether we
> --
> 2.26.3
>
next prev parent reply other threads:[~2022-02-11 22:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 22:44 [PATCH 0/8] Fix error handling on data bio submission Josef Bacik
2022-02-10 22:44 ` [PATCH 1/8] btrfs: make search_csum_tree return 0 if we get -EFBIG Josef Bacik
2022-02-11 22:39 ` Boris Burkov
2022-02-15 16:10 ` Johannes Thumshirn
2022-02-10 22:44 ` [PATCH 2/8] btrfs: handle csum lookup errors properly on reads Josef Bacik
2022-02-11 22:28 ` Boris Burkov
2022-02-10 22:44 ` [PATCH 3/8] btrfs: check correct bio in finish_compressed_bio_read Josef Bacik
2022-02-11 22:43 ` Boris Burkov
2022-02-16 8:48 ` Johannes Thumshirn
2022-02-10 22:44 ` [PATCH 4/8] btrfs: remove the bio argument from finish_compressed_bio_read Josef Bacik
2022-02-16 8:50 ` Johannes Thumshirn
2022-02-10 22:44 ` [PATCH 5/8] btrfs: track compressed bio errors as blk_status_t Josef Bacik
2022-02-16 8:53 ` Johannes Thumshirn
2022-02-10 22:44 ` [PATCH 6/8] btrfs: do not double complete bio on errors during compressed reads Josef Bacik
2022-02-11 22:54 ` Boris Burkov [this message]
2022-02-14 17:06 ` David Sterba
2022-02-10 22:44 ` [PATCH 7/8] btrfs: do not try to repair bio that has no mirror set Josef Bacik
2022-02-11 22:56 ` Boris Burkov
2022-02-10 22:44 ` [PATCH 8/8] btrfs: do not clean up repair bio if submit fails Josef Bacik
2022-02-11 23:00 ` 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=YgbpHjBvf49gtEbC@zen \
--to=boris@bur.io \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.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