qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* Does QEMU's coverity-scan run need to track coverity issues in dtb or slirp ?
@ 2020-11-02 19:54 Peter Maydell
  2020-11-02 20:37 ` Samuel Thibault
  2020-11-03  1:41 ` David Gibson
  0 siblings, 2 replies; 4+ messages in thread
From: Peter Maydell @ 2020-11-02 19:54 UTC (permalink / raw)
  To: QEMU Developers; +Cc: Samuel Thibault, David Gibson

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?

thanks
-- PMM


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2020-11-03  4:08 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).