All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <1643537@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1643537] Re: target-ppc/int_helper.c: 2 * bad array index
Date: Mon, 21 Nov 2016 15:15:23 -0000	[thread overview]
Message-ID: <20161121151523.8801.52650.malone@gac.canonical.com> (raw)
In-Reply-To: 20161121121617.5146.1948.malonedeb@wampee.canonical.com

Thanks for the bug report! Jose posted a patch:
marc.info/?i=1479740113-26834-1-git-send-email-joserz@linux.vnet.ibm.com

** Changed in: qemu
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1643537

Title:
  target-ppc/int_helper.c: 2 * bad array index

Status in QEMU:
  Confirmed

Bug description:
  1.

  [qemu/target-ppc/int_helper.c:2575]: (error) Array 'reg.u16[8]'
  accessed at index 8, which is out of bounds.

  Source code is

     return reg->u16[8 - n];

  and

  qemu/target-ppc/cpu.h:    uint16_t u16[8];

  but at least once, n is zero, for example line 2725 in the
  int_helper.c file:

      uint16_t sgnb = get_national_digit(b, 0);

  2.

  [qemu/target-ppc/int_helper.c:2584]: (error) Array 'reg.u16[8]'
  accessed at index 8, which is out of bounds.

  Duplicate

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1643537/+subscriptions

  parent reply	other threads:[~2016-11-21 15:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-21 12:16 [Qemu-devel] [Bug 1643537] [NEW] target-ppc/int_helper.c: 2 * bad array index dcb
2016-11-21 13:23 ` Thomas Huth
2016-11-21 14:58   ` joserz
2016-11-21 15:15 ` Thomas Huth [this message]
2016-12-07  8:40 ` [Qemu-devel] [Bug 1643537] " Thomas Huth
2017-01-16 11:37 ` Thomas Huth

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=20161121151523.8801.52650.malone@gac.canonical.com \
    --to=1643537@bugs.launchpad.net \
    --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.