From: Damien Le Moal <dlemoal@kernel.org>
To: "Martin K. Petersen" <martin.petersen@oracle.com>,
Yohan Joung <jyh429@gmail.com>
Cc: James.Bottomley@HansenPartnership.com,
linux-scsi@vger.kernel.org, Yohan Joung <yohan.joung@sk.com>
Subject: Re: [PATCH v1] scsi: Check the SPC version in sd_read_cpr
Date: Tue, 23 Jul 2024 09:57:45 +0900 [thread overview]
Message-ID: <aaad1a19-c68b-4269-a69a-039af87df019@kernel.org> (raw)
In-Reply-To: <yq1v80xc57l.fsf@ca-mkp.ca.oracle.com>
On 7/23/24 09:49, Martin K. Petersen wrote:
>
> Yohan,
>
>> Add SPC version verification to avoid unnecessary inquiry command
>
> Are you experiencing an actual error condition as a result of this
> INQUIRY operation?
>
> Devices often adopt new protocol features prior to the spec being
> finalized. Therefore we generally use INQUIRY to discover capabilities
> rather than relying on the reported spec compliance.
>
>> + /* Support for CPR was defined in SPC-5. */
>> + if (sdev->scsi_level < SCSI_SPC_5)
>> + return;
>> +
>
> I'm OK with the change but I'll defer to Damien as to whether this is an
> acceptable heuristic.
If this is solving an issue with an ATA device managed by libata, we can handle
that in libata. Otherwise, if this is an ATA device connected to a SAS HBA or a
SAS drive, then the issue could be with the HBA.
I missed this patch so I am not aware of the actual issue this is trying to solve...
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2024-07-23 0:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-20 15:00 [PATCH v1] scsi: Check the SPC version in sd_read_cpr Yohan Joung
2024-07-23 0:49 ` Martin K. Petersen
2024-07-23 0:57 ` Damien Le Moal [this message]
2024-07-23 2:08 ` Damien Le Moal
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=aaad1a19-c68b-4269-a69a-039af87df019@kernel.org \
--to=dlemoal@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=jyh429@gmail.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=yohan.joung@sk.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