All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jeffrey Karrels <karrelsj@gmail.com>
Cc: xen-devel@lists.xensource.com, Dario Faggioli <raistlin@linux.it>
Subject: Re: Static analysis: Code weaknesses
Date: Wed, 14 Mar 2012 14:58:23 -0400	[thread overview]
Message-ID: <20120314185823.GC5341@phenom.dumpdata.com> (raw)
In-Reply-To: <CAFw--DdRYLyEqyKm0h+mrasW_F=Akh_DuHbNHsiBJMrJAbLaLg@mail.gmail.com>

On Wed, Mar 14, 2012 at 11:01:08AM -0700, Jeffrey Karrels wrote:
> >> Have you looked at smatch and sparse?
> >>
> > And, perhaps, to Coccinelle (http://coccinelle.lip6.fr/)... I've heard
> > it does great things (together with Smatch) in Linux. :-)
> 
> Thanks, I will take a look.
> 
> Another question. There was mention of submitting Xen to Coverity a
> while back (Pratt 2006). Is there any reason not to submit the source

I am not sure what is involved in it? Is it free? If you are up for
doing it you are more than welcome to do it.

> into that as a project? I would be willing to be the point of contact,
> but am I stepping on anyone's toes if I submit it for scanning?
> 
> Thanks
> Jeff
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  reply	other threads:[~2012-03-14 18:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-09 18:10 Static analysis: Code weaknesses Jeffrey Karrels
2012-03-13 16:47 ` Konrad Rzeszutek Wilk
2012-03-13 17:03   ` Dario Faggioli
2012-03-14 18:01     ` Jeffrey Karrels
2012-03-14 18:58       ` Konrad Rzeszutek Wilk [this message]
2012-03-14 19:14         ` Jeffrey Karrels
2012-03-16 15:44           ` Jeffrey Karrels
2012-03-16 15:51             ` Konrad Rzeszutek Wilk
2012-03-16 16:10               ` Jeffrey Karrels
2012-09-05 20:13               ` Jeffrey Karrels

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=20120314185823.GC5341@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=karrelsj@gmail.com \
    --cc=raistlin@linux.it \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.