public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Jordi <mumismo@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Automatic bug hunting
Date: Thu, 8 Jun 2006 00:51:11 +0200	[thread overview]
Message-ID: <20060607225111.GV3955@stusta.de> (raw)
In-Reply-To: <200606080009.06089.raigengo@yahoo.es>

On Thu, Jun 08, 2006 at 12:09:04AM +0200, Jordi wrote:
> 
> Related with the recent times _perceived_  increase in the number of bugs of 
> the Kernel. I have found the following website:
> http://scan.coverity.com/
> 
> They use automatic statis source code test for a number of projects including 
> the Linux kernel.
> 
> I've not registered so I don't know what kind of bugs have been found but it's 
> very unlikely that they have found "I don't have the hardware to fix this" 
> kind of bugs. They surely are clear bugs, similar to those found by the 
> automatic test for locking problems. 

"They surely are clear bugs" is wrong, the proof is the trivial fact 
that not less than 148 kernel issues have already been marked as FALSE 
inside the Coverity tracker.

> I think this is a good source to check before doing a stable release. Unlikely  
> human's bugs report, those report should be clear enought. We may aim for 
> being "coverity free" before each major version (check it before 2.6.17).

If you'd have followed linux-kernel for a while, you'd have seen how 
many patches have already been sent and merged for issues listed there.

You can set any aim you want, but since the vast majority of these 
issues are not regressions from 2.6.16 there's no reason delaying 2.6.17 
for it.

Even more considering that even many of the Coverity issues are often 
harmless issues like e.g. dead code.

> Jordi Polo

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


      reply	other threads:[~2006-06-07 22:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-07 22:09 Automatic bug hunting Jordi
2006-06-07 22:51 ` Adrian Bunk [this message]

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=20060607225111.GV3955@stusta.de \
    --to=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mumismo@gmail.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