From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: WangYuli <wangyuli@uniontech.com>
Cc: James.Bottomley@HansenPartnership.com,
martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, stern@rowland.harvard.edu,
bvanassche@acm.org, zhanjun@uniontech.com,
niecheng1@uniontech.com, guanwentao@uniontech.com,
Xinwei Zhou <zhouxinwei@uniontech.com>,
Xu Rao <raoxu@uniontech.com>,
Yujing Ming <mingyujing@uniontech.com>
Subject: Re: [RESEND PATCH v3] scsi: Bypass certain SCSI commands on disks with "use_192_bytes_for_3f" attribute
Date: Thu, 20 Mar 2025 21:08:53 -0400 [thread overview]
Message-ID: <yq17c4j9pcr.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <798FB027101C5650+20250318061125.477498-1-wangyuli@uniontech.com> (wangyuli@uniontech.com's message of "Tue, 18 Mar 2025 14:11:25 +0800")
> However, "lshw" disregards the "use_192_bytes_for_3f" attribute and
> transmits data with a length of 0xff bytes via ioctl, which can cause
> some hard drives to hang and become unusable.
I am really not a fan of using in-kernel workarounds to intercept
passthrough commands.
Why does does lshw perform a MODE SENSE in the first place? What
information is it looking for that isn't available in sysfs?
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2025-03-21 1:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 6:11 [RESEND PATCH v3] scsi: Bypass certain SCSI commands on disks with "use_192_bytes_for_3f" attribute WangYuli
2025-03-21 1:08 ` Martin K. Petersen [this message]
2025-03-26 16:51 ` WangYuli
-- strict thread matches above, loose matches on Subject: below --
2025-02-24 3:48 WangYuli
2025-02-24 18:11 ` Bart Van Assche
2025-02-25 13:11 ` WangYuli
2025-02-25 20:54 ` Bart Van Assche
2025-02-26 2:31 ` WangYuli
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=yq17c4j9pcr.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bvanassche@acm.org \
--cc=guanwentao@uniontech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mingyujing@uniontech.com \
--cc=niecheng1@uniontech.com \
--cc=raoxu@uniontech.com \
--cc=stern@rowland.harvard.edu \
--cc=wangyuli@uniontech.com \
--cc=zhanjun@uniontech.com \
--cc=zhouxinwei@uniontech.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