From: Ben Chelf <ben@coverity.com>
To: linux-kernel@vger.kernel.org
Subject: Coverity Open Source Defect Scan of Linux
Date: Sun, 05 Mar 2006 21:35:11 -0800 [thread overview]
Message-ID: <440BCA0F.50501@coverity.com> (raw)
Hello Linux Developers,
I'm the CTO of Coverity, Inc., a company that does static source code
analysis to look for defects in code. You may have heard of us or of our
technology from its days at Stanford (the "Stanford Checker"). The
reason I'm writing is because we have set up a framework internally to
continually scan open source projects and provide the results of our
analysis back to the developers of those projects. Linux is one of the
32 projects currently scanned at:
http://scan.coverity.com
My belief is that we (Coverity) must reach out to the developers of
these packages (you) in order to make progress in actually fixing the
defects that we happen to find, so this is my first step in that
mission. Of course, I think Coverity technology is great, but I want to
hear what you think and that's why I worked with folks at Coverity to
put this infrastructure in place. The process is simple -- it checks out
your code each night from your repository and scans it so you can always
see the latest results.
Right now, we're guarding access to the actual defects that we report
for a couple of reasons: (1) We think that you, as developers of Linux,
should have the chance to look at the defects we find to patch them
before random other folks get to see what we found and (2) From a
support perspective, we want to make sure that we have the appropriate
time to engage with those who want to use the results to fix the code.
Because of this second point, I'd ask that if you are interested in
really digging into the results a bit further for your project, please
have a couple of core maintainers (or group nominated individuals) reach
out to me to request access. As this is a new process for us and still
involves a small number of packages, I want to make sure that I
personally can be involved with the activity that is generated from this
effort.
So I'm basically asking for people who want to play around with some
cool new technology to help make source code better. If this interests
you, please feel free to reach out to me directly. And of course, if
there are other packages you care about that aren't currently on the
list, I want to know about those too.
If this is the wrong list, my sincerest apologies and please let me
know where would be a more appropriate forum for this type of message.
Many thanks for reading this far...
-ben
Ben Chelf
Chief Technology Officer
Coverity, Inc.
next reply other threads:[~2006-03-06 5:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-06 5:35 Ben Chelf [this message]
2006-03-06 5:49 ` Coverity Open Source Defect Scan of Linux Dave Jones
2006-03-06 10:27 ` Adrian Bunk
2006-03-06 10:43 ` Bernd Petrovitsch
2006-03-06 11:03 ` Michal Schmidt
2006-03-06 11:08 ` Bernd Petrovitsch
2006-03-06 13:39 ` Ben Chelf
2006-03-06 11:57 ` Gene Heskett
2006-03-06 12:38 ` [OT] Linux washing powder (was: Re: Coverity Open Source Defect Scan of Linux) Michal Schmidt
2006-03-06 20:13 ` Gene Heskett
2006-03-06 13:07 ` Coverity Open Source Defect Scan of Linux Dick Streefland
2006-03-06 13:46 ` Ben Chelf
2006-03-06 15:46 ` Greg KH
2006-03-06 18:33 ` Pavel Machek
2006-03-06 18:53 ` Jesper Juhl
2006-03-14 12:37 ` Mauro Carvalho Chehab
2006-03-15 3:41 ` Lee Revell
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=440BCA0F.50501@coverity.com \
--to=ben@coverity.com \
--cc=linux-kernel@vger.kernel.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