From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: Aaron Elkins <threcius@yahoo.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-stable <qemu-stable@nongnu.org>,
patches@linaro.org
Subject: Re: [Qemu-devel] [PATCH for-2.5] hw/timer/hpet.c: Avoid signed integer overflow which results in bugs on OSX
Date: Mon, 9 Nov 2015 16:25:12 +0100 [thread overview]
Message-ID: <5640BAD8.9040005@redhat.com> (raw)
In-Reply-To: <1447080991-24995-1-git-send-email-peter.maydell@linaro.org>
On 09/11/2015 15:56, Peter Maydell wrote:
> Signed integer overflow in C is undefined behaviour, and the compiler
> is at liberty to assume it can never happen and optimize accordingly.
> In particular, the subtractions in hpet_time_after() and hpet_time_after64()
> were causing OSX clang to optimize the code such that it was prone to
> hangs and complaints about the main loop stalling (presumably because
> we were spending all our time trying to service very high frequency
> HPET timer callbacks). The clang sanitizer confirms the UB:
>
> hw/timer/hpet.c:119:26: runtime error: signed integer overflow: -2146967296 - 2147003978 cannot be represented in type 'int'
>
> Fix this by doing the subtraction as an unsigned operation and then
> converting to signed for the comparison.
>
> Reported-by: Aaron Elkins <threcius@yahoo.com>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> hw/timer/hpet.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/hw/timer/hpet.c b/hw/timer/hpet.c
> index 3037bef..7f0391c 100644
> --- a/hw/timer/hpet.c
> +++ b/hw/timer/hpet.c
> @@ -116,12 +116,12 @@ static uint32_t timer_enabled(HPETTimer *t)
>
> static uint32_t hpet_time_after(uint64_t a, uint64_t b)
> {
> - return ((int32_t)(b) - (int32_t)(a) < 0);
> + return ((int32_t)(b - a) < 0);
Does checkpatch complain about the outer parentheses?
> }
>
> static uint32_t hpet_time_after64(uint64_t a, uint64_t b)
> {
> - return ((int64_t)(b) - (int64_t)(a) < 0);
> + return ((int64_t)(b - a) < 0);
> }
Cc: qemu-stable@nongnu.org
Looks good, thanks! Can you apply it yourself?
Paolo
> static uint64_t ticks_to_ns(uint64_t value)
>
next prev parent reply other threads:[~2015-11-09 15:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 14:56 [Qemu-devel] [PATCH for-2.5] hw/timer/hpet.c: Avoid signed integer overflow which results in bugs on OSX Peter Maydell
2015-11-09 15:25 ` Paolo Bonzini [this message]
2015-11-09 15:26 ` Peter Maydell
2015-11-09 16:27 ` Peter Maydell
2015-11-09 20:17 ` Michael S. Tsirkin
2015-11-10 10:04 ` Peter Maydell
2015-11-10 11:57 ` Michael S. Tsirkin
2015-11-09 22:25 ` Laszlo Ersek
2015-11-10 8:57 ` Laszlo Ersek
2015-11-10 9:26 ` Paolo Bonzini
2015-11-10 9:51 ` Laszlo Ersek
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=5640BAD8.9040005@redhat.com \
--to=pbonzini@redhat.com \
--cc=mst@redhat.com \
--cc=patches@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=threcius@yahoo.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 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.