From: viro@parcelfarce.linux.theplanet.co.uk
To: "Robert T. Johnson" <rtjohnso@eecs.berkeley.edu>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Al Viro <viro@math.psu.edu>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Finding user/kernel pointer bugs
Date: Tue, 8 Jun 2004 01:03:10 +0100 [thread overview]
Message-ID: <20040608000310.GL12308@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <1086652124.14180.5.camel@dooby.cs.berkeley.edu>
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.
Another thing: two weeks had been enough to practically eliminate noise in
net/*, sound/*, large parts of drivers/*. The only real difficulty I've
noticed was one with holding the breakfast down while reading some of more...
colourful code.
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.
Now would it be too much to ask the esteemed sir to piss off and not return
until sir acquires a modicum of clue?
next prev parent reply other threads:[~2004-06-08 0:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-07 23:48 Finding user/kernel pointer bugs Robert T. Johnson
2004-06-08 0:03 ` viro [this message]
2004-06-08 1:03 ` Robert T. Johnson
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=20040608000310.GL12308@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rtjohnso@eecs.berkeley.edu \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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.