From: David Gibson <david@gibson.dropbear.id.au>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: agraf@suse.de, mst@redhat.com, qemu-ppc@nongnu.org,
rjones@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] i6300esb: Fix signed integer overflow
Date: Mon, 23 Mar 2015 11:18:26 +1100 [thread overview]
Message-ID: <20150323001826.GA25043@voom.fritz.box> (raw)
In-Reply-To: <550BE4B6.2040405@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2086 bytes --]
On Fri, Mar 20, 2015 at 10:13:26AM +0100, Paolo Bonzini wrote:
>
>
> On 20/03/2015 04:11, David Gibson wrote:
> > If the guest programs a sufficiently large timeout value an integer
> > overflow can occur in i6300esb_restart_timer(). e.g. if the maximum
> > possible timer preload value of 0xfffff is programmed then we end up with
> > the calculation:
> >
> > timeout = get_ticks_per_sec() * (0xfffff << 15) / 33000000;
> >
> > get_ticks_per_sec() returns 1000000000 (10^9) giving:
> >
> > 10^9 * (0xfffff * 2^15) == 0x1dcd632329b000000 (65 bits)
> >
> > Obviously the division by 33MHz brings it back under 64-bits, but the
> > overflow has already occurred.
> >
> > Since signed integer overflow has undefined behaviour in C, in theory this
> > could be arbitrarily bad. In practice, the overflowed value wraps around
> > to something negative, causing the watchdog to immediately expire, killing
> > the guest, which is still fairly bad.
> >
> > The bug can be triggered by running a Linux guest, loading the i6300esb
> > driver with parameter "heartbeat=2046" and opening /dev/watchdog. The
> > watchdog will trigger as soon as the device is opened.
> >
> > This patch corrects the problem by using an __int128_t temporary. With
> > suitable rearrangement of the calculations, I expect it would be possible
> > to avoid the __int128_t. But since we already use __int128_t extensively
> > in the memory region code, and this is not a hot path, the super-wide
> > integer seems like the simplest approach.
>
> We don't use __int128_t, we use the Int128 struct---which however
> doesn't have a multiplication function. __int128_t is not available on
> 32-bit machines, and is only used under #ifdef CONFIG_INT128.
>
> Instead, you can use muldiv64 which has exactly this purpose.
Ah, good point. I'll repost using muldiv64.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-03-23 0:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 3:11 [Qemu-devel] [PATCH 0/2] Fix bugs in i6300esb watchdog timer David Gibson
2015-03-20 3:11 ` [Qemu-devel] [PATCH 1/2] i6300esb: Correct endiannness David Gibson
2015-03-20 8:54 ` Richard W.M. Jones
2015-03-20 3:11 ` [Qemu-devel] [PATCH 2/2] i6300esb: Fix signed integer overflow David Gibson
2015-03-20 8:45 ` Richard W.M. Jones
2015-03-20 9:13 ` Paolo Bonzini
2015-03-23 0:18 ` David Gibson [this message]
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=20150323001826.GA25043@voom.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=agraf@suse.de \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=rjones@redhat.com \
/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).