From: "Robert T. Johnson" <rtjohnso@eecs.berkeley.edu>
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: Linus Torvalds <torvalds@transmeta.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Finding user/kernel pointer bugs
Date: 07 Jun 2004 18:03:29 -0700 [thread overview]
Message-ID: <1086656609.14180.16.camel@dooby.cs.berkeley.edu> (raw)
In-Reply-To: <20040608000310.GL12308@parcelfarce.linux.theplanet.co.uk>
On Mon, 2004-06-07 at 17:03, viro@parcelfarce.linux.theplanet.co.uk
wrote:
> On Mon, Jun 07, 2004 at 04:48:44PM -0700, Robert T. Johnson wrote:
> > - cqual requires _zero_ annotations in device drivers.
> >
> > Once the generic driver interfaces have been annotated, all device
> > drivers can be checked against these annotations without any further
> > effort. This is critical, since annotating the thousands of device
> > drivers in linux will be extremely difficult and take months.
>
> Aha, so you have never actually bothered to read the damn things. Two words:
> ioctl code.
CQual has already found numerous bugs in driver ioctl code, all without
any explicit annotations in that code. This is possible because cqual
infers the required annotations from a few annotations I gave it.
While examining these bugs, I had to read _a lot_ of driver code, and I
agree that some of it is very colorful.
> And one more: counting drivers that do not have a single __user in them
> is meaningless for so many reasons it's not even funny.
Maybe sparse has features that I don't know about, but since lots of
device drivers have ioctl functions, doesn't that mean that lots of
device drivers need at least one __user annotation (on the ioctl "arg"
argument)? If that annotation is missing and the device driver
dereferences arg (after casting it to a pointer), won't this result in a
false negative? I agree that it's not a perfect metric, but it's a
start.
Best,
Rob
next prev parent reply other threads:[~2004-06-08 1:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-07 23:48 Robert T. Johnson
2004-06-08 0:03 ` viro
2004-06-08 1:03 ` Robert T. Johnson [this message]
2004-06-08 2:52 ` viro
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=1086656609.14180.16.camel@dooby.cs.berkeley.edu \
--to=rtjohnso@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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
all inboxes | Powered by JetHome®