[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f02f049f-efa3-481b-b681-cf75308bfbc4@kernel.org>
Date: Fri, 22 Aug 2025 16:39:53 +0900
From: Damien Le Moal <dlemoal@...nel.org>
To: JiangJianJun <jiangjianjun3@...wei.com>,
James.Bottomley@...senPartnership.com, martin.petersen@...cle.com,
linux-scsi@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, hare@...e.de, bvanassche@....org,
michael.christie@...cle.com, hch@...radead.org, haowenchao22@...il.com,
john.g.garry@...cle.com, hewenliang4@...wei.com, yangyun50@...wei.com,
wuyifeng10@...wei.com, wubo40@...wei.com, yangxingui@...artners.com
Subject: Re: [PATCH 00/14] scsi: scsi_error: Introduce new error handle
mechanism
On 8/16/25 20:24, JiangJianJun wrote:
> It's unbearable for systems with large scale scsi devices share HBAs to
> block all devices' IOs when handle error commands, we need a new error
> handle mechanism to address this issue.
>
> I consulted about this issue a year ago, the discuss link can be found in
> refenence. Hannes replied about why we have to block the SCSI host
> then perform error recovery kindly. I think it's unnecessary to block
> SCSI host for all drivers and can try a small level recovery(LUN based for
> example) first to avoid block the SCSI host.
>
> The new error handle mechanism introduced in this patchset has been
> developed and tested with out self developed hardware since one year
> ago, now we want this mechanism can be used by more drivers.
>
> Drivers can decide if using the new error handle mechanism and how to
> handle error commands when scsi_device are scanned,the new mechanism
> makes SCSI error handle more flexible.
Barely half of your emails have made it through for me and they landed in my
spam folder. So please check your email setup.
Also, was this all tested with libata and libsas attached devices as well ?
They all depend on scsi EH.
--
Damien Le Moal
Western Digital Research
Powered by blists - more mailing lists