From: Greg KH <gregkh@linuxfoundation.org>
To: Shi Hao <i.shihao.999@gmail.com>
Cc: linux-usb@vger.kernel.org, stern@rowland.harvard.edu,
skhan@linuxfoundation.org
Subject: Re: [PATCH] usb: Implement proper subclass protocol translation
Date: Fri, 10 Oct 2025 14:29:05 +0200 [thread overview]
Message-ID: <2025101046-slogan-overlap-bbe4@gregkh> (raw)
In-Reply-To: <20251010113003.22863-1-i.shihao.999@gmail.com>
On Fri, Oct 10, 2025 at 05:00:03PM +0530, Shi Hao wrote:
> Proper protocol translation for old legacy usb devices.
>
> Earlier protocol translation was insufficient for old usb devices
> which was padding all subclasses such as USB_SC_RBC, USB_SC_SCSI
> and USB_SC_CYP_ATACB cmd_len to 6 byte value and because It wasn't
> complete It had a FIXME comment stating to fix the protocol transl
> -ation for those legacy usb devices.
>
> As a result implement proper protocol translation as per their op
> code.In addition to the old default value 6 those old legacy
> usb-device subclasses needed cmd_len value to 10, 12 , and 16
> byte also .
>
> Signed-off-by: Shi Hao <i.shihao.999@gmail.com>
> ---
> drivers/usb/storage/transport.c | 21 +++++++++++++++++----
> 1 file changed, 17 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/usb/storage/transport.c b/drivers/usb/storage/transport.c
> index 1aa1bd26c81f..4820b45d2a32 100644
> --- a/drivers/usb/storage/transport.c
> +++ b/drivers/usb/storage/transport.c
> @@ -718,12 +718,25 @@ void usb_stor_invoke_transport(struct scsi_cmnd *srb, struct us_data *us)
>
> scsi_eh_prep_cmnd(srb, &ses, NULL, 0, sense_size);
>
> - /* FIXME: we must do the protocol translation here */
> + /* Protocol translation per scsi opcode group */
> if (us->subclass == USB_SC_RBC || us->subclass == USB_SC_SCSI ||
> - us->subclass == USB_SC_CYP_ATACB)
> - srb->cmd_len = 6;
> - else
> + us->subclass == USB_SC_CYP_ATACB) {
> + /* Determine cmd_len based on scsi opcode group */
> + if (srb->cmnd[0] <= 0x1F)
> + srb->cmd_len = 6;
> + else if (srb->cmnd[0] <= 0x7F)
> + srb->cmd_len = 10;
> + else if (srb->cmnd[0] <= 0x9F)
> + srb->cmd_len = 16;
> + else if (srb->cmnd[0] <= 0xBF)
> + srb->cmd_len = 12;
> + else if (srb->cmnd[0] <= 0xDF)
> + srb->cmd_len = 16;
> + else
> + srb->cmd_len = 6;
> + } else {
> srb->cmd_len = 12;
> + }
>
> /* issue the auto-sense command */
> scsi_set_resid(srb, 0);
> --
> 2.51.0
>
Hi,
This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him
a patch that has triggered this response. He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created. Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.
You are receiving this message because of the following common error(s)
as indicated below:
- You did not write a descriptive Subject: for the patch, allowing Greg,
and everyone else, to know what this patch is all about. Please read
the section entitled "The canonical patch format" in the kernel file,
Documentation/process/submitting-patches.rst for what a proper
Subject: line should look like.
- This looks like a new version of a previously submitted patch, but you
did not list below the --- line any changes from the previous version.
Please read the section entitled "The canonical patch format" in the
kernel file, Documentation/process/submitting-patches.rst for what
needs to be done here to properly describe this.
If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.
thanks,
greg k-h's patch email bot
next prev parent reply other threads:[~2025-10-10 12:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 11:30 [PATCH] usb: Implement proper subclass protocol translation Shi Hao
2025-10-10 12:29 ` Greg KH [this message]
2025-10-10 15:07 ` Alan Stern
2025-10-11 9:37 ` ShiHao
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=2025101046-slogan-overlap-bbe4@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=i.shihao.999@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=stern@rowland.harvard.edu \
/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