From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] coverity-model: model address_space_read/write
Date: Wed, 15 Mar 2017 09:14:59 +0100 [thread overview]
Message-ID: <e8ffc658-88a5-4e4d-0b2e-159ee1609ef2@redhat.com> (raw)
In-Reply-To: <87mvcnnfbp.fsf@dusky.pond.sub.org>
On 15/03/2017 08:56, Markus Armbruster wrote:
> Paolo Bonzini <pbonzini@redhat.com> writes:
>
>> When more complexity was added to facilitate inlining, Coverity
>> lost the ability to use the address_space_rw model for
>> address_space_read/write.
>
> Got the commit hash of the change?
>
>> This causes false positive defects when Coverity sees
>> a length-8 write in address_space_read and a length-4
>> (e.g. int*) buffer to read into. As long as the size of
>> the buffer is okay, this is a false positive.
>>
>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>> ---
>> scripts/coverity-model.c | 19 +++++++++++++++++++
>> 1 file changed, 19 insertions(+)
>>
>> diff --git a/scripts/coverity-model.c b/scripts/coverity-model.c
>> index ee5bf9d..2e30150 100644
>> --- a/scripts/coverity-model.c
>> +++ b/scripts/coverity-model.c
>> @@ -79,6 +79,25 @@ MemTxResult address_space_rw(AddressSpace *as, hwaddr addr, MemTxAttrs attrs,
>> return result;
>> }
>>
>> +MemTxResult address_space_read(AddressSpace *as, hwaddr addr,
>> + MemTxAttrs attrs,
>> + uint8_t *buf, int len)
>> +{
>> + MemTxResult result;
>> + __bufwrite(buf, len);
>> + return result;
>> +}
>> +
>> +MemTxResult address_space_write(AddressSpace *as, hwaddr addr,
>> + MemTxAttrs attrs,
>> + const uint8_t *buf, int len)
>> +{
>> + MemTxResult result;
>> + __bufread(buf, len);
>> + return result;
>> +}
>> +
>> +
>> /* Tainting */
>>
>> typedef struct {} name2keysym_t;
>
> Preferably with the commit hash of the change that necessitates this
> update mentioned in the commit message:
> Reviewed-by: Markus Armbruster <armbru@redhat.com>
>
> I can stick this in a miscellaneous pull request due later today.
Commit eb7eeb8 ("memory: split address_space_read and
address_space_write", 2015-12-17). On the other hand, the model for
address_space_rw is not needed anymore, so I'll send v2.
Paolo
prev parent reply other threads:[~2017-03-15 8:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 11:39 [Qemu-devel] [PATCH] coverity-model: model address_space_read/write Paolo Bonzini
2017-03-15 7:56 ` Markus Armbruster
2017-03-15 8:14 ` Paolo Bonzini [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=e8ffc658-88a5-4e4d-0b2e-159ee1609ef2@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=qemu-devel@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).