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>
Subject: Re: [PATCH v3 08/13] md: remove MD_RECOVERY_ERROR handling and simplify resync_offset update
Date: Sat, 3 Jan 2026 18:36:01 +0800 [thread overview]
Message-ID: <74d80322-6a84-4d03-b09f-0f9dc5c1bec8@fnnas.com> (raw)
In-Reply-To: <20251215030444.1318434-9-linan666@huaweicloud.com>
在 2025/12/15 11:04, linan666@huaweicloud.com 写道:
> From: Li Nan<linan122@huawei.com>
>
> Following previous patch "md: update curr_resync_completed even when
> MD_RECOVERY_INTR is set", 'curr_resync_completed' always equals
> 'curr_resync' for resync, so MD_RECOVERY_ERROR can be removed.
>
> Also, simplify resync_offset update logic.
>
> Signed-off-by: Li Nan<linan122@huawei.com>
> ---
> drivers/md/md.h | 2 --
> drivers/md/md.c | 21 ++++-----------------
> 2 files changed, 4 insertions(+), 19 deletions(-)
Reviewed-by: Yu Kuai<yukuai@fnnas.com>
--
Thansk,
Kuai
next prev parent reply other threads:[~2026-01-03 10:36 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
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 [this message]
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=74d80322-6a84-4d03-b09f-0f9dc5c1bec8@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®