[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <ca3e635a-3fea-494e-9aa3-3c0ef5f58b13@fnnas.com>
Date: Sat, 3 Jan 2026 18:33:35 +0800
From: "Yu Kuai" <yukuai@...as.com>
To: <linan666@...weicloud.com>, <song@...nel.org>, <neil@...wn.name>,
<namhyung@...il.com>
Cc: <linux-raid@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<k@...l.me>, <yangerkun@...wei.com>, <yi.zhang@...wei.com>,
<yukuai@...as.com>
Subject: Re: [PATCH v3 07/13] md: update curr_resync_completed even when MD_RECOVERY_INTR is set
在 2025/12/15 11:04, linan666@...weicloud.com 写道:
> From: Li Nan<linan122@...wei.com>
>
> An error sync IO may be done and sub 'recovery_active' while its
> error handling work is pending. This work sets 'recovery_disabled'
> and MD_RECOVERY_INTR, then later removes the bad disk without Faulty
> flag. If 'curr_resync_completed' is updated before the disk is removed,
> it could lead to reading from sync-failed regions.
>
> With the previous patch, error IO will set badblocks or mark rdev as
> Faulty, sync-failed regions are no longer readable. After waiting for
> 'recovery_active' to reach 0 (in the previous line), all sync IO has
> *completed*, regardless of whether MD_RECOVERY_INTR is set. Thus, the
> MD_RECOVERY_INTR check can be removed.
>
> Signed-off-by: Li Nan<linan122@...wei.com>
> ---
> drivers/md/md.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Yu Kuai <yukuai@...as.com>
--
Thansk,
Kuai
Powered by blists - more mailing lists