From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3] coverity: Improve and extend model
Date: Wed, 28 Jan 2015 11:06:04 +0100 [thread overview]
Message-ID: <54C8B48C.40609@redhat.com> (raw)
In-Reply-To: <1422439112-12336-1-git-send-email-armbru@redhat.com>
On 28/01/2015 10:58, Markus Armbruster wrote:
> I examined the differences between local scans with and without a
> derived model file for GLib, to gauge what we're missing (the Coverity
> Scan service we use can't do derived model files). Doesn't look bad,
> but a few missed memory leaks caught my attention. I improved our
> model file to catch them (PATCH 1+2). Topped off with PATCH 3 to
> catch mixing up g_free() and free().
>
> Markus Armbruster (3):
> coverity: Improve model for GLib memory allocation
> coverity: Model GLib string allocation partially
> coverity: Model g_free() isn't necessarily free()
>
> scripts/coverity-model.c | 228 +++++++++++++++++++++++++++++++++++++++--------
> 1 file changed, 193 insertions(+), 35 deletions(-)
>
Acked-by: Paolo Bonzini <pbonzini@redhat.com>
It's missing a patch to add a MAINTAINERS entry though! :)
Paolo
next prev parent reply other threads:[~2015-01-28 10:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 9:58 [Qemu-devel] [PATCH 0/3] coverity: Improve and extend model Markus Armbruster
2015-01-28 9:58 ` [Qemu-devel] [PATCH 1/3] coverity: Improve model for GLib memory allocation Markus Armbruster
2015-01-28 9:58 ` [Qemu-devel] [PATCH 2/3] coverity: Model GLib string allocation partially Markus Armbruster
2015-01-28 9:58 ` [Qemu-devel] [PATCH 3/3] coverity: Model g_free() isn't necessarily free() Markus Armbruster
2015-01-28 10:06 ` Paolo Bonzini [this message]
2015-01-28 10:35 ` [Qemu-devel] [PATCH 0/3] coverity: Improve and extend model Markus Armbruster
2015-01-28 10:35 ` [Qemu-devel] [PATCH 4/3] MAINTAINERS: Add myself as Coverity model maintainer Markus Armbruster
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=54C8B48C.40609@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).