From: Paolo Bonzini <pbonzini@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] scripts: add sample model file for Coverity Scan
Date: Wed, 19 Mar 2014 20:46:14 +0100 [thread overview]
Message-ID: <5329F406.7040606@redhat.com> (raw)
In-Reply-To: <5329D4B7.4090602@redhat.com>
Il 19/03/2014 18:32, Eric Blake ha scritto:
>> + *
>> + * Copyright (C) 2014 Red Hat, Inc.
>> + *
>> + * Authors:
>> + * Markus Armbruster <armbru@redhat.com>
>> + * Paolo Bonzini <pbonzini@redhat.com>
>> + *
>> + * This work is licensed under the terms of the GNU GPL, version 2 or, at your
>> + * option, any later version. See the COPYING file in the top-level directory.
>
> Aren't the license and authors blurbs usually in the other order?
Not in the sample I copied from (migration.c).
>
>> +#define assert(x) if (!(x)) __coverity_panic__();
>
> Will this break any 'if () assert(); else {}' blocks? Obviously, such
> blocks already violate coding convention, but you might as well make
> this definition safe to use for older code.
Ok.
>> +
>> +static void __write(uint8_t *buf, int len)
>
> Will the fact that you used 'int len' instead of 'size_t' bite us on 32-
> vs. 64-bit? Same for __read.
Yeah, I copied this from address_space_rw. I'll change to ssize_t to
catch negative values.
>
>> +void *
>> +g_malloc0 (size_t n_bytes)
>> +{
>> + void *mem;
>> + __coverity_negative_sink__((ssize_t) n_bytes);
>> + mem = calloc(1, n_bytes == 0 ? 1 : n_bytes);
>> + if (!mem) __coverity_panic__ ();
>
> Is it worth being consistent on spacing before (?
Yes.
>> +void g_free (void *mem)
>> +{
>> + if (mem) {
>> + free(mem);
>> + }
>
> Doesn't coverity already know that free(NULL) is a no-op, without you
> having to repeat it?
This part came from Markus. :)
Paolo
next prev parent reply other threads:[~2014-03-19 19:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 16:52 [Qemu-devel] [PATCH v2] scripts: add sample model file for Coverity Scan Paolo Bonzini
2014-03-19 17:32 ` Eric Blake
2014-03-19 19:46 ` Paolo Bonzini [this message]
2014-03-20 7:32 ` Markus Armbruster
2014-03-20 13:01 ` Paolo Bonzini
2014-03-26 15:37 ` Markus Armbruster
2014-03-20 8:26 ` 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=5329F406.7040606@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@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).