From: Fabiano Rosas <farosas@suse.de>
To: Guenter Roeck <linux@roeck-us.net>,
Michael Tokarev <mjt@tls.msk.ru>, Hannes Reinecke <hare@suse.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, Fam Zheng <fam@euphon.net>,
qemu-block@nongnu.org, qemu-devel@nongnu.org,
qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [PATCH] scsi: megasas: Internal cdbs have 16-byte length
Date: Thu, 21 Nov 2024 15:53:11 -0300 [thread overview]
Message-ID: <87r0741krs.fsf@suse.de> (raw)
In-Reply-To: <6f2ba64a-dff1-49e7-bf81-4c1a7bf59494@roeck-us.net>
Guenter Roeck <linux@roeck-us.net> writes:
> On 2/17/24 01:06, Michael Tokarev wrote:
>>> 28.02.2023 20:11, Guenter Roeck wrote:
>>>> Host drivers do not necessarily set cdb_len in megasas io commands.
>>>> With commits 6d1511cea0 ("scsi: Reject commands if the CDB length
>>>> exceeds buf_len") and fe9d8927e2 ("scsi: Add buf_len parameter to
>>>> scsi_req_new()"), this results in failures to boot Linux from affected
>>>> SCSI drives because cdb_len is set to 0 by the host driver.
>>>> Set the cdb length to its actual size to solve the problem.
>>
>> Has this been lost/forgotten?
>>
>
> Not sure. My understanding was that I could not prove that this is how
> real hardware handles the situation, thus it wasn't applied. I carry it
> locally in my builds of qemu, so it is not a problem for me. Note that
> I didn't check if the problem has since been fixed differently. Maybe
> that is the case and the problem no longer exists in the upstream version
> of qemu.
The issue still happens upstream and I have just written the exact same
fix for it, so I'm adding my:
Reviewed-by: Fabiano Rosas <farosas@suse.de>
next prev parent reply other threads:[~2024-11-21 18:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 17:11 [PATCH] scsi: megasas: Internal cdbs have 16-byte length Guenter Roeck
2023-02-28 22:00 ` Philippe Mathieu-Daudé
2023-03-01 12:42 ` Michael Tokarev
2024-02-17 9:06 ` Michael Tokarev
2024-02-17 15:36 ` Guenter Roeck
2024-11-21 18:53 ` Fabiano Rosas [this message]
2023-03-03 9:02 ` Fiona Ebner
2023-03-03 15:10 ` Guenter Roeck
2023-03-06 7:36 ` Fiona Ebner
2024-11-21 19:41 ` Paolo Bonzini
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=87r0741krs.fsf@suse.de \
--to=farosas@suse.de \
--cc=fam@euphon.net \
--cc=hare@suse.com \
--cc=linux@roeck-us.net \
--cc=mjt@tls.msk.ru \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.