linux-kernel - Re: [PATCH 00/14] scsi: scsi_error: Introduce new error handle mechanism

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <c09657ab-95a4-4ffb-bddd-26babd1c803e@kernel.org>
Date: Tue, 2 Sep 2025 14:30:44 +0900
From: Damien Le Moal <dlemoal@...nel.org>
To: JiangJianJun <jiangjianjun3@...wei.com>, linux-scsi@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, hewenliang4@...wei.com,
 yangyun50@...wei.com, wuyifeng10@...wei.com, yangxingui@...artners.com
Subject: Re: [PATCH 00/14] scsi: scsi_error: Introduce new error handle
 mechanism

On 9/2/25 3:03 PM, JiangJianJun wrote:
>> Use write long command to "destroy" sectors. Then try to read them. That will
>> generate uncorrectable read errors.
> 
> There is a misunderstanding here, the condition that triggers this error
> handler is when the device is slow or unresponsive, or fails to start;
> bad blocks refer to data errors rather than faults.

You probably easilly can simulate an unresponsive device using either qemu or
tcmu-runner.


-- 
Damien Le Moal
Western Digital Research