From: John Richard Moser <nigelenki@comcast.net>
To: Rik van Riel <riel@redhat.com>
Cc: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] Bug zapper? :)
Date: Mon, 09 Aug 2004 23:13:24 -0400 [thread overview]
Message-ID: <41183D54.40603@comcast.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0408092246340.25913-100000@dhcp83-102.boston.redhat.com>
Rik van Riel wrote:
> On Mon, 9 Aug 2004, John Richard Moser wrote:
>
>
>>What I'm suggesting isn't much though, is it really?
>
>
> Then why haven't you done it already ? ;)
>
Alright, it's a big undertaking ;)
> On a more serious note, some other people are already
> auditing the code on a regular basis, while you weren't
> paying attention ...
>
I'm suggesting things to make code auditing simpler, more accurate, more
precise. "Quality-Assurance audited code still contains on average 5
bugs per kloc" is a really nasty thought.
http://lkml.org/lkml/2004/8/9/369 was the major explaination. It's big
and clunky to have before each function; but at least it's not ugly, and
it's potentially helpful. Maybe a few of the like in the smallest
driver possible to see how it feels? (/dev/mem?)
--
All content of all messages exchanged herein are left in the
Public Domain, unless otherwise explicitly stated.
next prev parent reply other threads:[~2004-08-10 3:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 20:07 [RFC] Bug zapper? :) John Richard Moser
[not found] ` <200408100042.37159.vda@port.imtp.ilyichevsk.odessa.ua>
2004-08-09 23:09 ` John Richard Moser
2004-08-10 0:58 ` Bernd Eckenfels
2004-08-10 1:55 ` Tommy Reynolds
2004-08-10 2:47 ` Rik van Riel
2004-08-10 3:13 ` John Richard Moser [this message]
2004-08-10 8:35 ` Jakob Oestergaard
2004-08-10 15:19 ` John Richard Moser
2004-08-10 21:43 ` Bernd Eckenfels
2004-08-10 21:30 ` V13
2004-08-10 23:35 ` John Richard Moser
2004-08-11 4:50 ` Bernd Eckenfels
-- strict thread matches above, loose matches on Subject: below --
2004-08-10 21:13 Nick Warne
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=41183D54.40603@comcast.net \
--to=nigelenki@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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