public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Damien Le Moal <dlemoal@kernel.org>
To: "Martin K . Petersen" <martin.petersen@oracle.com>,
	linux-scsi@vger.kernel.org
Cc: Igor Pylypiv <ipylypiv@google.com>
Subject: [PATCH v2] scsi: core: Disable CDL by default
Date: Fri,  7 Jun 2024 10:25:07 +0900	[thread overview]
Message-ID: <20240607012507.111488-1-dlemoal@kernel.org> (raw)

For scsi devices supporting the Command Duration Limits feature set, the
user can enable/disable this feature use through the sysfs device
attribute cdl_enable. This attribute modification triggers a call to
scsi_cdl_enable() to enable and disable the feature for ATA devices and
set the scsi device cdl_enable field to the user provided bool value.
For SCSI devices supporting CDL, the feature set is always enabled and
scsi_cdl_enable() is reduced to setting the cdl_enable field.

However, for ATA devices, a drive may spin-up with the CDL feature
enabled by default. But the scsi device cdl_enable field is always
initialized to false (CDL disabled), regardless of the actual device
CDL feature state. For ATA devices managed by libata (or libsas),
libata-core always disables the CDL feature set when the device is
attached, thus syncing the state of the CDL feature on the device and of
the scsi device cdl_enable field. However, for ATA devices connected to
a SAS HBA, the CDL feature is not disabled on scan for ATA devices that
have this feature enabled by default, leading to an inconsistent state
of the feature on the device with the scsi device cdl_enable field.

Avoid this inconsistency by adding a call to scsi_cdl_enable() in
scsi_cdl_check() to make sure that the device-side state of the CDL
feature set always matches the scsi device cdl_enable field state.
This implies that CDL will always be disabled for ATA devices connected
to SAS HBAs, which is consistent with libata/libsas initialization of
the device.

Reported-by: Scott McCoy <scott.mccoy@wdc.com>
Fixes: 1b22cfb14142 ("scsi: core: Allow enabling and disabling command duration limits")
Cc: stable@vger.kernel.org
Signed-off-by: Damien Le Moal <dlemoal@kernel.org>
---

Changes from v1:
 - Fixed typo in the commit title and improved the commit message

 drivers/scsi/scsi.c | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/drivers/scsi/scsi.c b/drivers/scsi/scsi.c
index 3e0c0381277a..9e9576066e8d 100644
--- a/drivers/scsi/scsi.c
+++ b/drivers/scsi/scsi.c
@@ -666,6 +666,13 @@ void scsi_cdl_check(struct scsi_device *sdev)
 		sdev->use_10_for_rw = 0;
 
 		sdev->cdl_supported = 1;
+
+		/*
+		 * If the device supports CDL, make sure that the current drive
+		 * feature status is consistent with the user controlled
+		 * cdl_enable state.
+		 */
+		scsi_cdl_enable(sdev, sdev->cdl_enable);
 	} else {
 		sdev->cdl_supported = 0;
 	}
-- 
2.45.2


             reply	other threads:[~2024-06-07  1:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-07  1:25 Damien Le Moal [this message]
2024-06-07  8:00 ` [PATCH v2] scsi: core: Disable CDL by default Niklas Cassel
2024-06-07 16:16 ` Igor Pylypiv
2024-06-11  6:27 ` Hannes Reinecke
2024-06-12  1:57 ` Martin K. Petersen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240607012507.111488-1-dlemoal@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=ipylypiv@google.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox