xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Coverity + XenProject + Process?
Date: Fri, 30 Aug 2013 16:34:39 +0100	[thread overview]
Message-ID: <5220BB8F.40502@citrix.com> (raw)
In-Reply-To: <20130830150053.GP21239@phenom.dumpdata.com>

On 30/08/13 16:00, Konrad Rzeszutek Wilk wrote:
> Hey
> 
> We have a static analyzer setup for Xen called Coverity. It allows
> the code to be inspected for bugs and such.
> 
> Originally I setup this so that we could make sure that there are no
> bugs that cause security issues - and as such invited only folks
> on the security Xen mailing list.

If there has been a pass already and that found no security issues, I
think the results should be made open and available to all.

Any (new) issues coverity might find in a development branch are just
bugs and not (yet) a security issues.

David

  reply	other threads:[~2013-08-30 15:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-30 15:00 Coverity + XenProject + Process? Konrad Rzeszutek Wilk
2013-08-30 15:34 ` David Vrabel [this message]
2013-08-30 16:08   ` Ian Campbell
2013-08-31  9:36 ` Ian Campbell
2013-08-31 21:50   ` Matt Wilson
2013-09-02  9:57     ` Lars Kurth
2013-09-04 17:14       ` Ian Campbell
2013-09-04 22:20       ` Steven Maresca
2013-09-04 22:25         ` Steven Maresca
2013-09-05  9:26 ` Ian Campbell
2013-09-06 13:33   ` Konrad Rzeszutek Wilk
2013-09-08 22:13   ` Matt Wilson
2013-09-09 13:30     ` Konrad Rzeszutek Wilk
2013-09-09 14:20       ` Ian Campbell
2013-09-09 19:08         ` Konrad Rzeszutek Wilk

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=5220BB8F.40502@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=xen-devel@lists.xensource.com \
    /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).