From: Cam Macdonell <cam@cs.ualberta.ca>
To: "Hao, Xudong" <xudong.hao@intel.com>
Cc: "Jes.Sorensen@redhat.com" <Jes.Sorensen@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH] hw/ivshmem.c don't check for negative values on unsigned data types
Date: Tue, 31 Aug 2010 21:56:24 -0600 [thread overview]
Message-ID: <AANLkTin7F5yxeHZ6UdGjJwwXu20sooRJc4D6b_hX6H9H@mail.gmail.com> (raw)
In-Reply-To: <BC00F5384FCFC9499AF06F92E8B78A9E18377521B5@shsmsx502.ccr.corp.intel.com>
On Tue, Aug 31, 2010 at 6:51 PM, Hao, Xudong <xudong.hao@intel.com> wrote:
> Hao, Xudong wrote:
>> Jes.Sorensen@redhat.com wrote:
>>> From: Jes Sorensen <Jes.Sorensen@redhat.com>
>>>
>>> There is no need to check for dest < 0 or vector >= 0 as both are
>>> uint16_t.
>>>
>>> This should fix problems with broken build with aggressive compiler
>>> flags. Reported by Xudong Hao <xudong.hao@intel.com>
>>>
>>> Signed-off-by: Jes Sorensen <Jes.Sorensen@redhat.com> ---
>>> hw/ivshmem.c | 4 ++--
>>> 1 files changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/hw/ivshmem.c b/hw/ivshmem.c
>>> index bbb5cba..afebbc3 100644
>>> --- a/hw/ivshmem.c
>>> +++ b/hw/ivshmem.c
>>> @@ -199,13 +199,13 @@ static void ivshmem_io_writel(void *opaque,
>>> target_phys_addr_t addr,
>>>
>>> case DOORBELL:
>>> /* check that dest VM ID is reasonable */
>>> - if ((dest < 0) || (dest > s->max_peer)) {
>>> + if (dest > s->max_peer) {
>>> IVSHMEM_DPRINTF("Invalid destination VM ID (%d)\n",
>>> dest); break;
>>> }
>>>
>>> /* check doorbell range */
>>> - if ((vector >= 0) && (vector <
>>> s->peers[dest].nb_eventfds)) { + if (vector <
>>> s->peers[dest].nb_eventfds) {
>>>
>>> IVSHMEM_DPRINTF("Writing %" PRId64 " to VM %d on
>>> vector %d\n", write_one, dest, vector); if
>>> (write(s->peers[dest].eventfds[vector],
>>
>> This patch works for me.
>>
>
> Jes, correct result is this patch works for me on x86_64 system. However, in i386 system, there is another bug:
>
> ...
> CC x86_64-softmmu/ivshmem.o
> CC x86_64-softmmu/fpu/softfloat-native.o
> CC x86_64-softmmu/op_helper.o
> cc1: warnings being treated as errors
> /home/build/gitrepo/qemu/hw/ivshmem.c: In function 'check_shm_size.
> /home/build/gitrepo/qemu/hw/ivshmem.c:357: warning: format '%ld' expects type 'long int', but argt 5 has type '__off64_t
> make[1]: *** [ivshmem.o] Error 1
> make[1]: *** Waiting for unfinished jobs....
> make: *** [subdir-x86_64-softmmu] Error 2
Hmm, that was causing problems on 32-bit systems, not 64-bit. Is this
with gcc 4.1.2? Please the try the following patch from Avi that
should add the necessary cast.
http://www.mail-archive.com/qemu-devel@nongnu.org/msg40715.html
Cam
next prev parent reply other threads:[~2010-09-01 3:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 10:31 [Qemu-devel] [PATCH] hw/ivshmem.c don't check for negative values on unsigned data types Jes.Sorensen
2010-08-31 6:01 ` [Qemu-devel] " Hao, Xudong
2010-09-01 0:51 ` Hao, Xudong
2010-09-01 3:56 ` Cam Macdonell [this message]
2010-09-01 4:00 ` [Qemu-devel] " Cam Macdonell
2010-09-01 3:53 ` Cam Macdonell
2010-09-04 10:06 ` [Qemu-devel] " Blue Swirl
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=AANLkTin7F5yxeHZ6UdGjJwwXu20sooRJc4D6b_hX6H9H@mail.gmail.com \
--to=cam@cs.ualberta.ca \
--cc=Jes.Sorensen@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xudong.hao@intel.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).