From: "Robert T. Johnson" <rtjohnso@eecs.berkeley.edu>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>,
"David S. Miller" <davem@redhat.com>,
Jeff Foster <jfoster@cs.berkeley.edu>,
David Wagner <daw@eecs.berkeley.edu>
Subject: CQual 0.99 Released: user/kernel pointer bug finding tool
Date: 10 Sep 2003 16:02:08 -0700 [thread overview]
Message-ID: <1063234934.19577.92.camel@dooby.cs.berkeley.edu> (raw)
In-Reply-To: <20030818210513.GB3276@kroah.com>
Download: http://www.cs.umd.edu/~jfoster/cqual/.
Support: cqual@cs.umd.edu.
CQual is a program verification tool that uses type-qualifier
inference to find bugs in C programs. This release of CQual includes
support for finding user/kernel pointer bugs in the linux kernel.
CQual has already found user/kernel pointer bugs in source files that
passed through Linus' "sparse" tool without generating any warnings.
Our goals with this release are
- help kernel developers avoid user/kernel bugs
- get feedback from kernel developers for future CQual features
CQual's current main features are:
- It requires _very_ few annotations: we currently use only ~200
- It's sound: CQual verifies the _absence_ of user/kernel bugs
- It generates fewer false warnings than sparse.
- It's context-sensitve: CQual doesn't confuse different calls to the
same function.
- CQual allows different instances of a struct type to hold different
kinds of pointers (i.e. user vs. kernel)
- It can be easily extended to find new types of bugs by editing a
configuration file
- It's fast: CQual analyzes most files in 1-2 seconds.
- It integrates easily into the kernel checking process.
The distribution contains a KERNEL-QUICKSTART to help kernel
developers start finding user/kernel bugs quickly. We look forward to
hearing your feedback.
CQual is currently developed by Jeff Foster, John Kodumal, Tachio
Terauchi, Rob Johnson, and many others.
Best,
Rob Johnson
next prev parent reply other threads:[~2003-09-10 23:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-03 17:23 PATCH: 2.4.22-pre7 drivers/i2c/i2c-dev.c user/kernel bug and mem leak Jean Delvare
2003-08-04 15:32 ` Sergey Vlasov
2003-08-05 8:32 ` Jean Delvare
2003-08-05 14:10 ` Sergey Vlasov
2003-08-05 21:07 ` Greg KH
2003-08-06 8:07 ` [PATCH 2.4] i2c-dev " Jean Delvare
[not found] ` <1060886657.1006.7121.camel@dooby.cs.berkeley.edu>
[not found] ` <20030814190954.GA2492@kroah.com>
2003-08-15 2:01 ` Robert T. Johnson
2003-08-15 21:13 ` Greg KH
2003-08-15 22:17 ` Robert T. Johnson
2003-08-15 23:51 ` Greg KH
2003-08-18 0:54 ` Robert T. Johnson
2003-08-18 21:05 ` Greg KH
2003-09-10 23:02 ` Robert T. Johnson [this message]
2003-08-28 1:17 ` Robert T. Johnson
2003-08-29 16:21 ` Jean Delvare
2003-08-29 17:30 ` Robert T. Johnson
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=1063234934.19577.92.camel@dooby.cs.berkeley.edu \
--to=rtjohnso@eecs.berkeley.edu \
--cc=davem@redhat.com \
--cc=daw@eecs.berkeley.edu \
--cc=greg@kroah.com \
--cc=jfoster@cs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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