linux-kernel - Re: [PATCH v7 5/7] scsi: hisi_sas: Add libsas SATA sysfs attributes group

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: <c1f8280b-3f8d-48ff-b5f3-40c3840f98e8@oracle.com>
Date: Thu, 7 Mar 2024 11:17:08 +0000
From: John Garry <john.g.garry@...cle.com>
To: Niklas Cassel <cassel@...nel.org>
Cc: Igor Pylypiv <ipylypiv@...gle.com>, Damien Le Moal <dlemoal@...nel.org>,
        Jason Yan <yanaijie@...wei.com>,
        "James E.J. Bottomley"
 <jejb@...ux.ibm.com>,
        "Martin K. Petersen" <martin.petersen@...cle.com>,
        Jack Wang <jinpu.wang@...ud.ionos.com>, Hannes Reinecke <hare@...e.de>,
        Xiang Chen <chenxiang66@...ilicon.com>,
        Artur Paszkiewicz <artur.paszkiewicz@...el.com>,
        Bart Van Assche <bvanassche@....org>, TJ Adams <tadamsjr@...gle.com>,
        linux-ide@...r.kernel.org, linux-scsi@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v7 5/7] scsi: hisi_sas: Add libsas SATA sysfs attributes
 group

> John, now I'm curious, do you know why hisi_sas_v1_hw.c is implemented
> as a libsas driver (instead of a regular SCSI driver), if it doesn't
> support SATA?

Using libsas is not really dependent on whether the HW supports SATA/STP 
or not. It's a protocol layer thing. Considering the SAS protocol stack, 
HW for drivers using libsas have implemented only the lower protocol 
layers, and SW, i.e. libsas, is required to manage upper layers, like 
Port layer and above.

BTW, IIRC, v1 hw did support SATA, but not STP, i.e. directly attached 
SATA only, but the SATA support was even more broken than v2 hw (which 
is quite broken), so never bothered supporting in SW.

> 
> Was perhaps v2_hw and v3_hw implemented as a libsas driver first
> (since they support SATA), and v1_hw support was added later,
> so that it could reuse much of the parts of the existing driver?

v1 driver support came first.

Thanks,
John