From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Su Yue <Damenly_Su@gmx.com>, Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: disk-io: Kill the BUG_ON()s in write_and_map_eb()
Date: Mon, 2 Mar 2020 12:45:39 +0800 [thread overview]
Message-ID: <f4f1e8da-8a3d-2413-1c83-6657d86170eb@gmx.com> (raw)
In-Reply-To: <m2r1ybctt9.fsf@gmx.com>
[-- Attachment #1.1: Type: text/plain, Size: 4531 bytes --]
On 2020/3/2 上午11:35, Su Yue wrote:
>
> On Mon 02 Mar 2020 at 09:41, Qu Wenruo <wqu@suse.com> wrote:
>
>> All callers of write_and_map_eb(), except btrfs-corrupt-block,
>> have handled error, but inside write_and_map_eb() itself, the
>> only error handling is BUG_ON().
>>
>> This patch will kill all the BUG_ON()s inside
>> write_and_map_eb(), and enhance the the caller in
>> btrfs-corrupt-block() to handle the error.
>>
>> Signed-off-by: Qu Wenruo <wqu@suse.com> ---
>> btrfs-corrupt-block.c | 9 ++++++++-
>> cmds/rescue-super-recover.c | 3 ++-
>
> So may the subject be prefixed with "btrfs-progs"?
>
>> disk-io.c | 26 +++++++++++++++++++++++--- 3
>> files changed, 33 insertions(+), 5 deletions(-)
>>
>> diff --git a/btrfs-corrupt-block.c b/btrfs-corrupt-block.c index
>> 95df871a7822..3c236e146176 100644 --- a/btrfs-corrupt-block.c
>> +++ b/btrfs-corrupt-block.c @@ -771,8 +771,15 @@ static int
>> corrupt_metadata_block(struct btrfs_fs_info *fs_info, u64 block,
>> u64 bogus = generate_u64(orig);
>> btrfs_set_header_generation(eb, bogus);
>> - write_and_map_eb(fs_info, eb); + ret =
>> write_and_map_eb(fs_info, eb);
>> free_extent_buffer(eb);
>> + if (ret < 0) { + errno = -ret; +
>> fprintf(stderr, + "failed to write extent buffer at
>> %llu: %m", + eb->start); + return ret; +
>> }
>> break; } case BTRFS_METADATA_BLOCK_SHIFT_ITEMS:
>> diff --git a/cmds/rescue-super-recover.c
>> b/cmds/rescue-super-recover.c index 5d6bea836c8b..62f4f7754720
>> 100644 --- a/cmds/rescue-super-recover.c +++
>> b/cmds/rescue-super-recover.c @@ -276,7 +276,8 @@ int
>> btrfs_recover_superblocks(const char *dname,
>> struct super_block_record, list); root =
>> open_ctree(record->device_name, record->bytenr,
>> - OPEN_CTREE_RECOVER_SUPER | OPEN_CTREE_WRITES); +
>> OPEN_CTREE_RECOVER_SUPER | OPEN_CTREE_WRITES | +
>> OPEN_CTREE_EXCLUSIVE);
>
> Any explanation about this change?
My bad, unclean base.
I'll resend the patch.
Thanks,
Qu
>
> Thanks
>
>> if (!root) {
>> ret = 3;
>> goto no_recover;
>> diff --git a/disk-io.c b/disk-io.c
>> index e8a2e4afa93a..9ff62fcd54d1 100644
>> --- a/disk-io.c
>> +++ b/disk-io.c
>> @@ -487,20 +487,40 @@ int write_and_map_eb(struct btrfs_fs_info
>> *fs_info, struct extent_buffer *eb)
>> length = eb->len;
>> ret = btrfs_map_block(fs_info, WRITE, eb->start, &length,
>> &multi, 0, &raid_map);
>> + if (ret < 0) {
>> + errno = -ret;
>> + error("failed to map bytenr %llu length %u: %m",
>> + eb->start, eb->len);
>> + goto out;
>> + }
>>
>> if (raid_map) {
>> ret = write_raid56_with_parity(fs_info, eb, multi,
>> length, raid_map);
>> - BUG_ON(ret);
>> + if (ret < 0) {
>> + errno = -ret;
>> + error(
>> + "failed to write raid56 stripe for bytenr %llu length %llu: %m",
>> + eb->start, length);
>> + goto out;
>> + }
>> } else while (dev_nr < multi->num_stripes) {
>> - BUG_ON(ret);
>> eb->fd = multi->stripes[dev_nr].dev->fd;
>> eb->dev_bytenr = multi->stripes[dev_nr].physical;
>> multi->stripes[dev_nr].dev->total_ios++;
>> dev_nr++;
>> ret = write_extent_to_disk(eb);
>> - BUG_ON(ret);
>> + if (ret < 0) {
>> + errno = -ret;
>> + error(
>> +"failed to write bytenr %llu length %u devid %llu dev_bytenr %llu: %m",
>> + eb->start, eb->len,
>> + multi->stripes[dev_nr].dev->devid,
>> + eb->dev_bytenr);
>> + goto out;
>> + }
>> }
>> +out:
>> kfree(raid_map);
>> kfree(multi);
>> return 0;
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-03-02 4:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 1:41 [PATCH] btrfs: disk-io: Kill the BUG_ON()s in write_and_map_eb() Qu Wenruo
2020-03-02 3:35 ` Su Yue
2020-03-02 4:45 ` Qu Wenruo [this message]
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=f4f1e8da-8a3d-2413-1c83-6657d86170eb@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=Damenly_Su@gmx.com \
--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