From: John Garry <john.g.garry@oracle.com>
To: Yu Kuai <yukuai1@huaweicloud.com>,
axboe@kernel.dk, song@kernel.org, hch@lst.de
Cc: martin.petersen@oracle.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
hare@suse.de, Johannes.Thumshirn@wdc.com,
"yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [PATCH v2 7/7] md/raid10: Handle bio_split() errors
Date: Tue, 29 Oct 2024 12:05:19 +0000 [thread overview]
Message-ID: <f0ecb0b1-7963-42ed-a26d-9b155884abb6@oracle.com> (raw)
In-Reply-To: <eeb9ca32-6862-6a07-bc51-7bd05430f018@huaweicloud.com>
On 29/10/2024 11:55, Yu Kuai wrote:
> Hi,
>
> 在 2024/10/28 23:27, John Garry 写道:
>> Add proper bio_split() error handling. For any error, call
>> raid_end_bio_io() and return. Except for discard, where we end the bio
>> directly.
>>
>> Signed-off-by: John Garry <john.g.garry@oracle.com>
>> ---
>> drivers/md/raid10.c | 47 ++++++++++++++++++++++++++++++++++++++++++++-
>> 1 file changed, 46 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/md/raid10.c b/drivers/md/raid10.c
>> index f3bf1116794a..9c56b27b754a 100644
>> --- a/drivers/md/raid10.c
>> +++ b/drivers/md/raid10.c
>> @@ -1159,6 +1159,7 @@ static void raid10_read_request(struct mddev
>> *mddev, struct bio *bio,
>> int slot = r10_bio->read_slot;
>> struct md_rdev *err_rdev = NULL;
>> gfp_t gfp = GFP_NOIO;
>> + int error;
>> if (slot >= 0 && r10_bio->devs[slot].rdev) {
>> /*
>> @@ -1206,6 +1207,10 @@ static void raid10_read_request(struct mddev
>> *mddev, struct bio *bio,
>> if (max_sectors < bio_sectors(bio)) {
>> struct bio *split = bio_split(bio, max_sectors,
>> gfp, &conf->bio_split);
>> + if (IS_ERR(split)) {
>> + error = PTR_ERR(split);
>> + goto err_handle;
>> + }
>> bio_chain(split, bio);
>> allow_barrier(conf);
>> submit_bio_noacct(bio);
>> @@ -1236,6 +1241,12 @@ static void raid10_read_request(struct mddev
>> *mddev, struct bio *bio,
>> mddev_trace_remap(mddev, read_bio, r10_bio->sector);
>> submit_bio_noacct(read_bio);
>> return;
>> +err_handle:
>> + atomic_dec(&rdev->nr_pending);
>
> I just realized that for the raid1 patch, this is missed. read_balance()
> from raid1 will increase nr_pending as well. :(
hmmm... I have the rdev_dec_pending() call for raid1 at the error label,
which does the appropriate nr_pending dec, right? Or not?
>
>> +
>> + bio->bi_status = errno_to_blk_status(error);
>> + set_bit(R10BIO_Uptodate, &r10_bio->state);
>> + raid_end_bio_io(r10_bio);
>> }
>> static void raid10_write_one_disk(struct mddev *mddev, struct r10bio
>> *r10_bio,
>> @@ -1347,9 +1358,10 @@ static void raid10_write_request(struct mddev
>> *mddev, struct bio *bio,
>> struct r10bio *r10_bio)
>> {
>> struct r10conf *conf = mddev->private;
>> - int i;
>> + int i, k;
>> sector_t sectors;
>> int max_sectors;
>> + int error;
>> if ((mddev_is_clustered(mddev) &&
>> md_cluster_ops->area_resyncing(mddev, WRITE,
>> @@ -1482,6 +1494,10 @@ static void raid10_write_request(struct mddev
>> *mddev, struct bio *bio,
>> if (r10_bio->sectors < bio_sectors(bio)) {
>> struct bio *split = bio_split(bio, r10_bio->sectors,
>> GFP_NOIO, &conf->bio_split);
>> + if (IS_ERR(split)) {
>> + error = PTR_ERR(split);
>> + goto err_handle;
>> + }
>> bio_chain(split, bio);
>> allow_barrier(conf);
>> submit_bio_noacct(bio);
>> @@ -1503,6 +1519,25 @@ static void raid10_write_request(struct mddev
>> *mddev, struct bio *bio,
>> raid10_write_one_disk(mddev, r10_bio, bio, true, i);
>> }
>> one_write_done(r10_bio);
>> + return;
>> +err_handle:
>> + for (k = 0; k < i; k++) {
>> + struct md_rdev *rdev, *rrdev;
>> +
>> + rdev = conf->mirrors[k].rdev;
>> + rrdev = conf->mirrors[k].replacement;
>
> This looks wrong, r10_bio->devs[k].devnum should be used to deference
> rdev from mirrors.
ok
>> +
>> + if (rdev)
>> + rdev_dec_pending(conf->mirrors[k].rdev, mddev);
>> + if (rrdev)
>> + rdev_dec_pending(conf->mirrors[k].rdev, mddev);
>
> This is not correct for now, for the case that rdev is all BB in the
> write range, continue will be reached in the loop and rrdev is skipped(
> This doesn't look correct to skip rrdev). However, I'll suggest to use:
>
> int d = r10_bio->devs[k].devnum;
> if (r10_bio->devs[k].bio == NULL)
eh, should this be:
if (r10_bio->devs[k].bio != NULL)
> rdev_dec_pending(conf->mirrors[d].rdev);
> if (r10_bio->devs[k].repl_bio == NULL)
> rdev_dec_pending(conf->mirrors[d].replacement);
>
>
>> + r10_bio->devs[k].bio = NULL;
>> + r10_bio->devs[k].repl_bio = NULL;
>> + }
>> +
>> + bio->bi_status = errno_to_blk_status(error);
>> + set_bit(R10BIO_Uptodate, &r10_bio->state);
>> + raid_end_bio_io(r10_bio);
Thanks,
John
next prev parent reply other threads:[~2024-10-29 12:06 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 15:27 [PATCH v2 0/7] bio_split() error handling rework John Garry
2024-10-28 15:27 ` [PATCH v2 1/7] block: Use BLK_STS_OK in bio_init() John Garry
2024-10-28 16:11 ` Christoph Hellwig
2024-10-28 16:32 ` John Garry
2024-10-28 15:27 ` [PATCH v2 2/7] block: Rework bio_split() return value John Garry
2024-10-28 16:12 ` Christoph Hellwig
2024-10-29 9:12 ` Johannes Thumshirn
2024-10-28 15:27 ` [PATCH v2 3/7] block: Error an attempt to split an atomic write in bio_split() John Garry
2024-10-28 16:12 ` Christoph Hellwig
2024-10-29 9:12 ` Johannes Thumshirn
2024-10-28 15:27 ` [PATCH v2 4/7] block: Handle bio_split() errors in bio_submit_split() John Garry
2024-10-28 16:12 ` Christoph Hellwig
2024-10-29 9:13 ` Johannes Thumshirn
2024-10-28 15:27 ` [PATCH v2 5/7] md/raid0: Handle bio_split() errors John Garry
2024-10-29 3:52 ` Yu Kuai
2024-10-28 15:27 ` [PATCH v2 6/7] md/raid1: " John Garry
2024-10-29 3:48 ` Yu Kuai
2024-10-29 8:45 ` John Garry
2024-10-29 11:30 ` Yu Kuai
2024-10-29 11:36 ` John Garry
2024-10-29 11:32 ` Yu Kuai
2024-10-29 12:12 ` Yu Kuai
2024-10-29 12:21 ` John Garry
2024-10-28 15:27 ` [PATCH v2 7/7] md/raid10: " John Garry
2024-10-29 11:55 ` Yu Kuai
2024-10-29 12:05 ` John Garry [this message]
2024-10-29 12:10 ` Yu Kuai
2024-10-29 9:11 ` [PATCH] btrfs: handle bio_split() error Johannes Thumshirn
2024-10-29 10:33 ` John Garry
2024-10-30 14:00 ` kernel test robot
2024-10-30 14:06 ` Johannes Thumshirn
2024-10-30 14:20 ` John Garry
2024-10-30 14:29 ` Johannes Thumshirn
2024-10-30 20:05 ` Dan Carpenter
2024-10-31 9:29 ` John Garry
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=f0ecb0b1-7963-42ed-a26d-9b155884abb6@oracle.com \
--to=john.g.garry@oracle.com \
--cc=Johannes.Thumshirn@wdc.com \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=song@kernel.org \
--cc=yukuai1@huaweicloud.com \
--cc=yukuai3@huawei.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
all inboxes | Powered by JetHome®