From: David Gibson <david@gibson.dropbear.id.au>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: Does QEMU's coverity-scan run need to track coverity issues in dtb or slirp ?
Date: Tue, 3 Nov 2020 12:41:43 +1100 [thread overview]
Message-ID: <20201103014143.GF143651@yekko.fritz.box> (raw)
In-Reply-To: <CAFEAcA93d5VKj+jbJQcyxsG+54G32r1k53DPT8rGRqZcROU2hA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1085 bytes --]
On Mon, Nov 02, 2020 at 07:54:14PM +0000, Peter Maydell wrote:
> Currently QEMU's Coverity-Scan project has a bunch of unresolved
> issues in code in dtc/ and also in slirp/. (I suspect most of them
> are actually false-positives that got re-reported when we switched
> to Meson and the filenames changed, or some similar event.)
>
> Do dtc and slirp as upstream projects already track Coverity issues
> (in which case we can just close the issues in the QEMU tracker as
> irrelevant, or do we need to investigate these and potentially
> forward them into whatever upstream bug tracker is appropriate?
dtc is wired up to coverity_scan, and quite a few of the things it
caught were fixed a while back. I must admit I don't re-examine the
remaining warnings very frequently though. I *think* what's still
there are false positives, but I'm not super confident about that.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-11-03 4:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 19:54 Does QEMU's coverity-scan run need to track coverity issues in dtb or slirp ? Peter Maydell
2020-11-02 20:37 ` Samuel Thibault
2020-11-02 22:23 ` Peter Maydell
2020-11-03 1:41 ` David Gibson [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=20201103014143.GF143651@yekko.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=samuel.thibault@ens-lyon.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).