Message ID | 20240813131900.1285842-2-cassel@kernel.org |
---|---|
State | New |
Headers | show |
Series | Revert "ata: libata-scsi: Honor the D_SENSE bit for CK_COND=1 and no error" | expand |
Niklas, > This reverts commit 28ab9769117ca944cb6eb537af5599aa436287a4. Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
On 8/13/24 15:19, Niklas Cassel wrote: > This reverts commit 28ab9769117ca944cb6eb537af5599aa436287a4. > > Sense data can be in either fixed format or descriptor format. > > SAT-6 revision 1, "10.4.6 Control mode page", defines the D_SENSE bit: > "The SATL shall support this bit as defined in SPC-5 with the following > exception: if the D_ SENSE bit is set to zero (i.e., fixed format sense > data), then the SATL should return fixed format sense data for ATA > PASS-THROUGH commands." > > The libata SATL has always kept D_SENSE set to zero by default. (It is > however possible to change the value using a MODE SELECT SG_IO command.) > > Failed ATA PASS-THROUGH commands correctly respected the D_SENSE bit, > however, successful ATA PASS-THROUGH commands incorrectly returned the > sense data in descriptor format (regardless of the D_SENSE bit). > > Commit 28ab9769117c ("ata: libata-scsi: Honor the D_SENSE bit for > CK_COND=1 and no error") fixed this bug for successful ATA PASS-THROUGH > commands. > > However, after commit 28ab9769117c ("ata: libata-scsi: Honor the D_SENSE > bit for CK_COND=1 and no error"), there were bug reports that hdparm, > hddtemp, and udisks were no longer working as expected. > > These applications incorrectly assume the returned sense data is in > descriptor format, without even looking at the RESPONSE CODE field in the > returned sense data (to see which format the returned sense data is in). > > Considering that there will be broken versions of these applications around > roughly forever, we are stuck with being bug compatible with older kernels. > > Cc: stable@vger.kernel.org # 4.19+ > Reported-by: Stephan Eisvogel <eisvogel@seitics.de> > Reported-by: Christian Heusel <christian@heusel.eu> > Closes: https://lore.kernel.org/linux-ide/0bf3f2f0-0fc6-4ba5-a420-c0874ef82d64@heusel.eu/ > Fixes: 28ab9769117c ("ata: libata-scsi: Honor the D_SENSE bit for CK_COND=1 and no error") > Signed-off-by: Niklas Cassel <cassel@kernel.org> > --- > drivers/ata/libata-scsi.c | 15 +++++++++++++-- > 1 file changed, 13 insertions(+), 2 deletions(-) > Reviewed-by: Hannes Reinecke <hare@suse.de> Cheers, Hannes
On Tue, 13 Aug 2024 15:19:01 +0200, Niklas Cassel wrote: > This reverts commit 28ab9769117ca944cb6eb537af5599aa436287a4. > > Sense data can be in either fixed format or descriptor format. > > SAT-6 revision 1, "10.4.6 Control mode page", defines the D_SENSE bit: > "The SATL shall support this bit as defined in SPC-5 with the following > exception: if the D_ SENSE bit is set to zero (i.e., fixed format sense > data), then the SATL should return fixed format sense data for ATA > PASS-THROUGH commands." > > [...] Applied to libata/linux.git (for-6.11-fixes), thanks! [1/1] Revert "ata: libata-scsi: Honor the D_SENSE bit for CK_COND=1 and no error" https://git.kernel.org/libata/linux/c/fa0db8e5 Kind regards, Niklas
diff --git a/drivers/ata/libata-scsi.c b/drivers/ata/libata-scsi.c index d6f5e25e1ed8..473e00a58a8b 100644 --- a/drivers/ata/libata-scsi.c +++ b/drivers/ata/libata-scsi.c @@ -951,8 +951,19 @@ static void ata_gen_passthru_sense(struct ata_queued_cmd *qc) &sense_key, &asc, &ascq); ata_scsi_set_sense(qc->dev, cmd, sense_key, asc, ascq); } else { - /* ATA PASS-THROUGH INFORMATION AVAILABLE */ - ata_scsi_set_sense(qc->dev, cmd, RECOVERED_ERROR, 0, 0x1D); + /* + * ATA PASS-THROUGH INFORMATION AVAILABLE + * + * Note: we are supposed to call ata_scsi_set_sense(), which + * respects the D_SENSE bit, instead of unconditionally + * generating the sense data in descriptor format. However, + * because hdparm, hddtemp, and udisks incorrectly assume sense + * data in descriptor format, without even looking at the + * RESPONSE CODE field in the returned sense data (to see which + * format the returned sense data is in), we are stuck with + * being bug compatible with older kernels. + */ + scsi_build_sense(cmd, 1, RECOVERED_ERROR, 0, 0x1D); } }
This reverts commit 28ab9769117ca944cb6eb537af5599aa436287a4. Sense data can be in either fixed format or descriptor format. SAT-6 revision 1, "10.4.6 Control mode page", defines the D_SENSE bit: "The SATL shall support this bit as defined in SPC-5 with the following exception: if the D_ SENSE bit is set to zero (i.e., fixed format sense data), then the SATL should return fixed format sense data for ATA PASS-THROUGH commands." The libata SATL has always kept D_SENSE set to zero by default. (It is however possible to change the value using a MODE SELECT SG_IO command.) Failed ATA PASS-THROUGH commands correctly respected the D_SENSE bit, however, successful ATA PASS-THROUGH commands incorrectly returned the sense data in descriptor format (regardless of the D_SENSE bit). Commit 28ab9769117c ("ata: libata-scsi: Honor the D_SENSE bit for CK_COND=1 and no error") fixed this bug for successful ATA PASS-THROUGH commands. However, after commit 28ab9769117c ("ata: libata-scsi: Honor the D_SENSE bit for CK_COND=1 and no error"), there were bug reports that hdparm, hddtemp, and udisks were no longer working as expected. These applications incorrectly assume the returned sense data is in descriptor format, without even looking at the RESPONSE CODE field in the returned sense data (to see which format the returned sense data is in). Considering that there will be broken versions of these applications around roughly forever, we are stuck with being bug compatible with older kernels. Cc: stable@vger.kernel.org # 4.19+ Reported-by: Stephan Eisvogel <eisvogel@seitics.de> Reported-by: Christian Heusel <christian@heusel.eu> Closes: https://lore.kernel.org/linux-ide/0bf3f2f0-0fc6-4ba5-a420-c0874ef82d64@heusel.eu/ Fixes: 28ab9769117c ("ata: libata-scsi: Honor the D_SENSE bit for CK_COND=1 and no error") Signed-off-by: Niklas Cassel <cassel@kernel.org> --- drivers/ata/libata-scsi.c | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-)