From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: <qemu-devel@nongnu.org>, <marcel@redhat.com>, <qemu-trivial@nongnu.org>
Subject: Re: [Qemu-trivial] [PATCH] pcie: remove duplicate assertion
Date: Tue, 10 Jan 2017 16:46:04 +0800 [thread overview]
Message-ID: <58749F4C.9080902@cn.fujitsu.com> (raw)
In-Reply-To: <20170110003733-mutt-send-email-mst@kernel.org>
On 01/10/2017 06:37 AM, Michael S. Tsirkin wrote:
> On Fri, Dec 23, 2016 at 10:16:30AM +0800, Cao jin wrote:
>> "size >= 8" connote "size > 0"
>>
>> Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com>
>
> Isn't the point to check for overflows?
>
Make sense. If it is intended to check overflows, the following sequence
would make more sense:
assert(offset >= PCI_CONFIG_SPACE_SIZE);
assert(size >= 8);
assert(offset < offset + size);
assert(offset + size <= PCIE_CONFIG_SPACE_SIZE);
or else, size 0 will pass the assert(offset < offset + size) first and
hit assert(size >= 8)
--
Sincerely,
Cao jin
>> ---
>> hw/pci/pcie.c | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/hw/pci/pcie.c b/hw/pci/pcie.c
>> index 39b10b852d91..f864c5cd5458 100644
>> --- a/hw/pci/pcie.c
>> +++ b/hw/pci/pcie.c
>> @@ -668,7 +668,6 @@ void pcie_add_capability(PCIDevice *dev,
>> uint16_t next;
>>
>> assert(offset >= PCI_CONFIG_SPACE_SIZE);
>> - assert(offset < offset + size);
>> assert(offset + size <= PCIE_CONFIG_SPACE_SIZE);
>> assert(size >= 8);
>> assert(pci_is_express(dev));
>> --
>> 2.1.0
>>
>>
>
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, marcel@redhat.com, qemu-trivial@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] pcie: remove duplicate assertion
Date: Tue, 10 Jan 2017 16:46:04 +0800 [thread overview]
Message-ID: <58749F4C.9080902@cn.fujitsu.com> (raw)
In-Reply-To: <20170110003733-mutt-send-email-mst@kernel.org>
On 01/10/2017 06:37 AM, Michael S. Tsirkin wrote:
> On Fri, Dec 23, 2016 at 10:16:30AM +0800, Cao jin wrote:
>> "size >= 8" connote "size > 0"
>>
>> Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com>
>
> Isn't the point to check for overflows?
>
Make sense. If it is intended to check overflows, the following sequence
would make more sense:
assert(offset >= PCI_CONFIG_SPACE_SIZE);
assert(size >= 8);
assert(offset < offset + size);
assert(offset + size <= PCIE_CONFIG_SPACE_SIZE);
or else, size 0 will pass the assert(offset < offset + size) first and
hit assert(size >= 8)
--
Sincerely,
Cao jin
>> ---
>> hw/pci/pcie.c | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/hw/pci/pcie.c b/hw/pci/pcie.c
>> index 39b10b852d91..f864c5cd5458 100644
>> --- a/hw/pci/pcie.c
>> +++ b/hw/pci/pcie.c
>> @@ -668,7 +668,6 @@ void pcie_add_capability(PCIDevice *dev,
>> uint16_t next;
>>
>> assert(offset >= PCI_CONFIG_SPACE_SIZE);
>> - assert(offset < offset + size);
>> assert(offset + size <= PCIE_CONFIG_SPACE_SIZE);
>> assert(size >= 8);
>> assert(pci_is_express(dev));
>> --
>> 2.1.0
>>
>>
>
>
>
next prev parent reply other threads:[~2017-01-10 8:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-23 2:16 [Qemu-trivial] [PATCH] pcie: remove duplicate assertion Cao jin
2016-12-23 2:16 ` [Qemu-devel] " Cao jin
2017-01-09 22:37 ` [Qemu-trivial] " Michael S. Tsirkin
2017-01-09 22:37 ` [Qemu-devel] " Michael S. Tsirkin
2017-01-10 8:46 ` Cao jin [this message]
2017-01-10 8:46 ` Cao jin
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=58749F4C.9080902@cn.fujitsu.com \
--to=caoj.fnst@cn.fujitsu.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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.