mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Yu Kuai" <yukuai@fnnas.com>
To: <linan666@huaweicloud.com>, <song@kernel.org>, <neil@brown.name>,
	 <namhyung@gmail.com>
Cc: <linux-raid@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	 <k@mgml.me>, <yangerkun@huawei.com>, <yi.zhang@huawei.com>,
	 <yukuai@fnnas.com>
Subject: Re: [PATCH v3 03/13] md/raid1,raid10: return actual write status in narrow_write_error
Date: Sat, 3 Jan 2026 18:16:32 +0800	[thread overview]
Message-ID: <b4abf0b4-6df2-442e-8549-a409cd24e989@fnnas.com> (raw)
In-Reply-To: <e429dabc-8f93-44a2-9024-1d9c669ef800@fnnas.com>

Hi,

在 2026/1/3 17:37, Yu Kuai 写道:
> Hi,
>
> 在 2025/12/15 11:04, linan666@huaweicloud.com 写道:
>> From: Li Nan <linan122@huawei.com>
>>
>> narrow_write_error() currently returns true when setting badblocks fails.

I think you mean rewrite failed and set badblocks succeed.

>> Instead, return actual status of all retried writes, succeeding only when
>> all retried writes complete successfully. This gives upper layers accurate
>> information about write outcomes.
>>
>> When setting badblocks fails, mark the device as faulty and return at once.
>> No need to continue processing remaining sections in such cases.
>>
>> Signed-off-by: Li Nan <linan122@huawei.com>
>> ---
>>    drivers/md/raid1.c  | 17 +++++++++--------
>>    drivers/md/raid10.c | 15 +++++++++------
>>    2 files changed, 18 insertions(+), 14 deletions(-)
>>
>> diff --git a/drivers/md/raid1.c b/drivers/md/raid1.c
>> index 90ad9455f74a..9ffa3ab0fdcc 100644
>> --- a/drivers/md/raid1.c
>> +++ b/drivers/md/raid1.c
>> @@ -2541,11 +2541,15 @@ static bool narrow_write_error(struct r1bio *r1_bio, int i)
>>    		bio_trim(wbio, sector - r1_bio->sector, sectors);
>>    		wbio->bi_iter.bi_sector += rdev->data_offset;
>>    
>> -		if (submit_bio_wait(wbio) < 0)
>> +		if (submit_bio_wait(wbio)) {
>>    			/* failure! */
>> -			ok = rdev_set_badblocks(rdev, sector,
>> -						sectors, 0)
>> -				&& ok;
>> +			ok = false;
>> +			if (!rdev_set_badblocks(rdev, sector, sectors, 0)) {
>> +				md_error(mddev, rdev);
>> +				bio_put(wbio);
>> +				break;
>> +			}
>> +		}
>>    
>>    		bio_put(wbio);
>>    		sect_to_write -= sectors;
>> @@ -2596,10 +2600,7 @@ static void handle_write_finished(struct r1conf *conf, struct r1bio *r1_bio)
>>    			 * errors.
>>    			 */
>>    			fail = true;
>> -			if (!narrow_write_error(r1_bio, m))
>> -				md_error(conf->mddev,
>> -					 conf->mirrors[m].rdev);
>> -				/* an I/O failed, we can't clear the bitmap */
>> +			narrow_write_error(r1_bio, m);
> I remembered that I said please change this helper to void.

take a look back after patch 4, I still think this should be void.

>
>>    			rdev_dec_pending(conf->mirrors[m].rdev,
>>    					 conf->mddev);
>>    		}
>> diff --git a/drivers/md/raid10.c b/drivers/md/raid10.c
>> index 40c31c00dc60..21a347c4829b 100644
>> --- a/drivers/md/raid10.c
>> +++ b/drivers/md/raid10.c
>> @@ -2820,11 +2820,15 @@ static bool narrow_write_error(struct r10bio *r10_bio, int i)
>>    				   choose_data_offset(r10_bio, rdev);
>>    		wbio->bi_opf = REQ_OP_WRITE;
>>    
>> -		if (submit_bio_wait(wbio) < 0)
>> +		if (submit_bio_wait(wbio)) {
>>    			/* Failure! */
>> -			ok = rdev_set_badblocks(rdev, wsector,
>> -						sectors, 0)
>> -				&& ok;
>> +			ok = false;
>> +			if (!rdev_set_badblocks(rdev, wsector, sectors, 0)) {
>> +				md_error(mddev, rdev);
>> +				bio_put(wbio);
>> +				break;
>> +			}
>> +		}
>>    
>>    		bio_put(wbio);
>>    		sect_to_write -= sectors;
>> @@ -2936,8 +2940,7 @@ static void handle_write_completed(struct r10conf *conf, struct r10bio *r10_bio)
>>    				rdev_dec_pending(rdev, conf->mddev);
>>    			} else if (bio != NULL && bio->bi_status) {
>>    				fail = true;
>> -				if (!narrow_write_error(r10_bio, m))
>> -					md_error(conf->mddev, rdev);
>> +				narrow_write_error(r10_bio, m);
>>    				rdev_dec_pending(rdev, conf->mddev);
>>    			}
>>    			bio = r10_bio->devs[m].repl_bio;

-- 
Thansk,
Kuai

  reply	other threads:[~2026-01-03 10:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-15  3:04 [PATCH v3 00/13] cleanup and bugfix of sync linan666
2025-12-15  3:04 ` [PATCH v3 01/13] md/raid1: simplify uptodate handling in end_sync_write linan666
2025-12-15  3:04 ` [PATCH v3 02/13] md: factor error handling out of md_done_sync into helper linan666
2025-12-15  3:04 ` [PATCH v3 03/13] md/raid1,raid10: return actual write status in narrow_write_error linan666
2026-01-03  9:37   ` Yu Kuai
2026-01-03 10:16     ` Yu Kuai [this message]
2025-12-15  3:04 ` [PATCH v3 04/13] md/raid1,raid10: set Uptodate and clear badblocks if narrow_write_error success linan666
2026-01-03 10:16   ` Yu Kuai
2025-12-15  3:04 ` [PATCH v3 05/13] md/raid1,raid10: support narrow_write_error when badblocks is disabled linan666
2026-01-03 10:23   ` Yu Kuai
2025-12-15  3:04 ` [PATCH v3 06/13] md: mark rdev Faulty when badblocks setting fails linan666
2025-12-15  3:04 ` [PATCH v3 07/13] md: update curr_resync_completed even when MD_RECOVERY_INTR is set linan666
2026-01-03 10:33   ` Yu Kuai
2025-12-15  3:04 ` [PATCH v3 08/13] md: remove MD_RECOVERY_ERROR handling and simplify resync_offset update linan666
2026-01-03 10:36   ` Yu Kuai
2025-12-15  3:04 ` [PATCH v3 09/13] md: factor out sync completion update into helper linan666
2025-12-15  3:04 ` [PATCH v3 10/13] md: move finish_reshape to md_finish_sync() linan666
2025-12-15  3:04 ` [PATCH v3 11/13] md/raid10: fix any_working flag handling in raid10_sync_request linan666
2025-12-15  3:04 ` [PATCH v3 12/13] md/raid10: cleanup skip " linan666
2025-12-15  3:04 ` [PATCH v3 13/13] md: remove recovery_disabled linan666

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=b4abf0b4-6df2-442e-8549-a409cd24e989@fnnas.com \
    --to=yukuai@fnnas.com \
    --cc=k@mgml.me \
    --cc=linan666@huaweicloud.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=namhyung@gmail.com \
    --cc=neil@brown.name \
    --cc=song@kernel.org \
    --cc=yangerkun@huawei.com \
    --cc=yi.zhang@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®