From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] scsi-bus: Fix transfer length for VERIFY with BYTCHK=11b
Date: Wed, 29 Jan 2014 18:51:03 +0100 [thread overview]
Message-ID: <52E93F87.5040600@redhat.com> (raw)
In-Reply-To: <1391017659-5506-1-git-send-email-armbru@redhat.com>
Il 29/01/2014 18:47, Markus Armbruster ha scritto:
> The transfer length depends on field BYTCHK, which is encoded in byte
> 1, bits 1..2. However, the guard for for case BYTCHK=11b doesn't
> work, and we get case 01b instead. Fix it.
>
> Note that since emulated scsi-hd fails the command outright, it takes
> SCSI passthrough of a device that actually implements VERIFY with
> BYTCHK=11b to make the bug bite.
>
> Screwed up in commit d12ad44. Spotted by Coverity.
>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
> hw/scsi/scsi-bus.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/scsi/scsi-bus.c b/hw/scsi/scsi-bus.c
> index 50b89ad..285a58b 100644
> --- a/hw/scsi/scsi-bus.c
> +++ b/hw/scsi/scsi-bus.c
> @@ -909,7 +909,7 @@ static int scsi_req_length(SCSICommand *cmd, SCSIDevice *dev, uint8_t *buf)
> case VERIFY_16:
> if ((buf[1] & 2) == 0) {
> cmd->xfer = 0;
> - } else if ((buf[1] & 4) == 1) {
> + } else if ((buf[1] & 4) != 0) {
> cmd->xfer = 1;
> }
> cmd->xfer *= dev->blocksize;
>
Applied to scsi-next, thanks.
Paolo
next prev parent reply other threads:[~2014-01-29 17:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 17:47 [Qemu-devel] [PATCH] scsi-bus: Fix transfer length for VERIFY with BYTCHK=11b Markus Armbruster
2014-01-29 17:51 ` Paolo Bonzini [this message]
2014-02-24 13:07 ` Markus Armbruster
2014-02-24 13:25 ` 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=52E93F87.5040600@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=qemu-devel@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.