[an error occurred while processing this directive]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <daefef14-c1de-48f1-992d-f8dbe1c7504e@fnnas.com>
Date: Thu, 30 Oct 2025 10:41:51 +0800
From: "Yu Kuai" <yukuai@...as.com>
To: "Kenta Akagi" <k@...l.me>, "Song Liu" <song@...nel.org>, 
	"Shaohua Li" <shli@...com>, "Mariusz Tkaczyk" <mtkaczyk@...nel.org>
Cc: <linux-raid@...r.kernel.org>, <linux-kernel@...r.kernel.org>, 
	"Li Nan" <linan122@...wei.com>, <yukuai@...as.com>
Subject: Re: [PATCH v5 09/16] md/raid10: fix failfast read error not rescheduled

在 2025/10/27 23:04, Kenta Akagi 写道:

> raid10_end_read_request lacks a path to retry when a FailFast IO fails.
> As a result, when Failfast Read IOs fail on all rdevs, the upper layer
> receives EIO, without read rescheduled.
>
> Looking at the two commits below, it seems only raid10_end_read_request
> lacks the failfast read retry handling, while raid1_end_read_request has
> it. In RAID1, the retry works as expected.
> * commit 8d3ca83dcf9c ("md/raid10: add failfast handling for reads.")
> * commit 2e52d449bcec ("md/raid1: add failfast handling for reads.")
>
> This commit will make the failfast read bio for the last rdev in raid10
> retry if it fails.
>
> Fixes: 8d3ca83dcf9c ("md/raid10: add failfast handling for reads.")
> Signed-off-by: Kenta Akagi<k@...l.me>
> Reviewed-by: Li Nan<linan122@...wei.com>
> ---
>   drivers/md/raid10.c | 7 +++++++
>   1 file changed, 7 insertions(+)

Reviewed-by: Yu Kuai <yukuai@...as.com>