qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	The OpenBIOS Mailinglist <openbios@openbios.org>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] hw/scsi-bus.c: Fix use of uninitialised variable
Date: Sun, 14 Aug 2011 19:32:45 +0200	[thread overview]
Message-ID: <4E4806BD.5010309@redhat.com> (raw)
In-Reply-To: <CAAu8pHsjVWN7t238CEWkeypbB6GEdmdAw=eWjMr9SqXUyuG=8Q@mail.gmail.com>

On 08/13/2011 07:29 PM, Blue Swirl wrote:
> On Fri, Aug 12, 2011 at 7:22 PM, Blue Swirl<blauwirbel@gmail.com>  wrote:
>> On Fri, Aug 12, 2011 at 4:49 PM, Peter Maydell<peter.maydell@linaro.org>  wrote:
>>> Don't use req before it has been initialised in scsi_req_new().
>>> This fixes a compile failure due to gcc complaining about this.
>>
>> It fixes a crash if the warning is ignored:
>> Configuration device id QEMU version 1 machine id 32

Please apply it.

> This is due to division by zero in OpenBIOS drivers/esp.c. Bisecting
> reveals that this is due to c7b488721d6aafe32994ac63f8d690ae6d4729fa,
> SCSI devices now report Unit Attention status after reset. OpenBIOS
> does not handle this case and fails (block size is 0).
>
> First OpenBIOS issues Inquiry command, then if a device is present,
> Read Capacity. I tried adding Request Sense command after Inquiry, but
> then QEMU crashes:

Thanks, I'll look into this.  However, not that Inquiry will not report 
unit attention.  The right fix is to send a Test Unit Ready after 
Inquiry and until it passes (and fail after 3/4 tries).

Paolo

  reply	other threads:[~2011-08-14 17:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-12 16:49 [Qemu-devel] [PATCH] hw/scsi-bus.c: Fix use of uninitialised variable Peter Maydell
2011-08-12 19:22 ` Blue Swirl
2011-08-13 17:29   ` Blue Swirl
2011-08-14 17:32     ` Paolo Bonzini [this message]
2011-08-14 18:03 ` Paolo Bonzini
2011-08-14 20:00 ` Blue Swirl

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=4E4806BD.5010309@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=blauwirbel@gmail.com \
    --cc=openbios@openbios.org \
    --cc=peter.maydell@linaro.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).