qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] scripts: add sample model file for Coverity Scan
Date: Wed, 19 Mar 2014 13:46:04 +0100	[thread overview]
Message-ID: <5329918C.8090403@redhat.com> (raw)
In-Reply-To: <87d2hi4ktz.fsf@blackfin.pond.sub.org>

Il 19/03/2014 10:08, Markus Armbruster ha scritto:
>> It probably would make static analysis a bit less powerful or will
>> return more false positives.  The NULL return for realloc (in the
>> "free" case) already causes some.  So I'm undecided between a more
>> correct model and a more selective one (with a fat comment).
>
> I can't see how lying to the analyzer could make it more powerful :)
> It can, however, suppress false positives.  Scan and find out how many?

Full model (g_malloc returns NULL for 0 argument) => 750 defects

Posted model (g_malloc never returns NULL)        => 702 defects
		-59 NULL_RETURNS defects
		 -1 REVERSE_INULL defects
		+12 TAINTED_SCALAR defects

Reduced model (g_realloc never frees)             => 690 defects
		-12 NULL_RETURNS defects

Of course, silly me, I threw away the results of the analysis for the 
full model.  I'll now rerun it and look for false negatives caused by 
the reduced model.

Paolo

  reply	other threads:[~2014-03-19 12:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-18 17:03 [Qemu-devel] [PATCH] scripts: add sample model file for Coverity Scan Paolo Bonzini
2014-03-18 18:40 ` Markus Armbruster
2014-03-19  7:03   ` Paolo Bonzini
2014-03-19  9:08     ` Markus Armbruster
2014-03-19 12:46       ` Paolo Bonzini [this message]
2014-03-19 13:56         ` Paolo Bonzini
2014-03-19 14:57           ` Paolo Bonzini
2014-03-19 15:56             ` Markus Armbruster
2014-03-19 16:47               ` Paolo Bonzini
2014-03-19  9:36 ` Kevin Wolf

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=5329918C.8090403@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=armbru@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 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).