linux-kernel - Re: [PATCH] scsi: sd: retry command SYNC CACHE if format in progress

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: <yq1h6bpxmiw.fsf@ca-mkp.ca.oracle.com>
Date: Mon, 12 Aug 2024 21:33:29 -0400
From: "Martin K. Petersen" <martin.petersen@...cle.com>
To: Bart Van Assche <bvanassche@....org>
Cc: Yihang Li <liyihang9@...wei.com>, James.Bottomley@...senPartnership.com,
        martin.petersen@...cle.com, linux-scsi@...r.kernel.org,
        linux-kernel@...r.kernel.org, prime.zeng@...wei.com,
        linuxarm@...wei.com
Subject: Re: [PATCH] scsi: sd: retry command SYNC CACHE if format in progress

> It seems like the PCI core supports binding and unbinding through
> sysfs but the SCSI core not. So it's probably easier to add support
> for ASC/ASCQ 04h / 04h rather than to add bind/unbind support to the
> SCSI core.

I am not a fan of trying to cover all these revalidation corner cases.
Having the ULD attached during a format operation makes zero sense.

NVMe handles formatting and a few other commands differently based on
the Commands Supported and Effects Log Page. The SCSI protocol doesn't
have the same elaborate reporting scheme but that doesn't mean we
couldn't handle disruptive operations similar to what the NVMe driver is
doing.

-- 
Martin K. Petersen	Oracle Linux Engineering