From: Alexander Graf <agraf@suse.de>
To: David Gibson <david@gibson.dropbear.id.au>, armbru@redhat.com
Cc: aik@ozlabs.ru, qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
mdroth@us.ibm.com
Subject: Re: [Qemu-devel] [PATCH] spapr_pci: Fix unsafe signed/unsigned comparisons
Date: Fri, 20 Mar 2015 12:38:10 +0100 [thread overview]
Message-ID: <550C06A2.6000402@suse.de> (raw)
In-Reply-To: <1426738458-24229-1-git-send-email-david@gibson.dropbear.id.au>
On 19.03.15 05:14, David Gibson wrote:
> spapr_pci.c contains a number of expressions of the form (uval == -1) or
> (uval != -1), where 'uval' is an unsigned value.
>
> This mostly works in practice, because as long as the width of uval is
> greater or equal than that of (int), the -1 will be promoted to the
> unsigned type, which is the expected outcome.
>
> However, at least for the cases where uval is uint32_t, this would break
> on platforms where sizeof(int) > 4 (and a few such do exist), because then
> the uint32_t value would be promoted to the larger int type, and never be
> equal to -1.
>
> This patch fixes these errors. The fixes for the (uint32_t) cases are
> necessary as described above. I've made similar fixes to (uint64_t) and
> (hwaddr) cases. Those are strictly theoretical, since I don't know of any
> platforms where sizeof(int) > 8, but hey, it's not that hard so we might
> as well be strictly C standard compliant.
>
> Reported-by: Markus Armbruster <armbru@redhat.com>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Thanks, applied to ppc-next-2.4.
Alex
prev parent reply other threads:[~2015-03-20 11:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 4:14 [Qemu-devel] [PATCH] spapr_pci: Fix unsafe signed/unsigned comparisons David Gibson
2015-03-20 8:37 ` Markus Armbruster
2015-03-20 11:38 ` Alexander Graf [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=550C06A2.6000402@suse.de \
--to=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=armbru@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=mdroth@us.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).