qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [RESEND PATCH for-1.5] acpi: add dummy write function for acpi timer
Date: Tue, 14 May 2013 14:45:30 +0200	[thread overview]
Message-ID: <519231EA.3060202@redhat.com> (raw)
In-Reply-To: <1368534544-11826-1-git-send-email-kraxel@redhat.com>

On 05/14/13 14:29, Gerd Hoffmann wrote:
> Otherwise the guest can crash qemu (NULL pointer dereference).
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=947691
> 
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> ---
>  hw/acpi/core.c |    7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/hw/acpi/core.c b/hw/acpi/core.c
> index 64b8718..42eeace 100644
> --- a/hw/acpi/core.c
> +++ b/hw/acpi/core.c
> @@ -462,8 +462,15 @@ static uint64_t acpi_pm_tmr_read(void *opaque, hwaddr addr, unsigned width)
>      return acpi_pm_tmr_get(opaque);
>  }
>  
> +static void acpi_pm_tmr_write(void *opaque, hwaddr addr, uint64_t val,
> +                              unsigned width)
> +{
> +    /* nothing */
> +}
> +
>  static const MemoryRegionOps acpi_pm_tmr_ops = {
>      .read = acpi_pm_tmr_read,
> +    .write = acpi_pm_tmr_write,
>      .valid.min_access_size = 4,
>      .valid.max_access_size = 4,
>      .endianness = DEVICE_LITTLE_ENDIAN,
> 

(Hopefully the low-hanging fruit impression it makes is not a trap!)

Reviewed-by: Laszlo Ersek <lersek@redhat.com>

  reply	other threads:[~2013-05-14 12:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-14 12:29 [Qemu-devel] [RESEND PATCH for-1.5] acpi: add dummy write function for acpi timer Gerd Hoffmann
2013-05-14 12:45 ` Laszlo Ersek [this message]
2013-05-14 16:10 ` Anthony Liguori

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=519231EA.3060202@redhat.com \
    --to=lersek@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=mst@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 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).