From: "Natalie Protasevich" <protasnb@gmail.com>
To: "Arjan van de Ven" <arjan@infradead.org>
Cc: "Adrian Bunk" <bunk@kernel.org>,
"Bosko Radivojevic" <bosko.radivojevic@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Number of bugs - statistics
Date: Thu, 22 May 2008 08:47:36 -0700 [thread overview]
Message-ID: <32209efe0805220847h5495fd7ctf1c3b9fdd387ec2d@mail.gmail.com> (raw)
In-Reply-To: <20080522075135.4933161c@infradead.org>
On Thu, May 22, 2008 at 7:51 AM, Arjan van de Ven <arjan@infradead.org> wrote:
> On Thu, 22 May 2008 17:41:14 +0300
> Adrian Bunk <bunk@kernel.org> wrote:
>
>> On Thu, May 22, 2008 at 02:28:17PM +0200, Bosko Radivojevic wrote:
>>
>> > Hi!
>>
>> Hi Bosko!
>>
>> > Is there any kind of analysis of number of (reported or resolved)
>> > bugs through time in Linux kernel floating around? I'm trying to
>> > convince my colleagues that newer kernel version does not mean more
>> > bugs than the previous 'well tested' ones.
>>
>> We definitely have many regressions (something that previously worked
>> does no longer work) in each kernel.
>
> ... and many of those regressions are things people are unlikely to
> hit. And we fix many long standing bugs as well.
>
> Maybe some other data:
> * The incoming rate of ACPI bugs has been pretty much flat the last 3
> years, while the number of Linux (and ACPI) users has grown
> significantly. The number of unfixed bugs has more than halved, from
> over 200 to well below 100.
> * The SCSI maintainer also reports that he sees flat to declining bug
> rates; again with the increase in Linux user base that is a good sign
>
>
>>
>> > Any kind of (research) reports or papers that address this issue is
>> > more than welcome.
>>
>> Any such reports or papers would anyway be flawed since we have no
>> data one could use for doing serious statistics.
>
> We have data for 2.6.25 at least, on which we can and do serious
> statistics. Unfortunately we don't have that for older kernels.
> What we have for older kernels only comes from lkml reports (which
> isn't very representative), but that shows that the bug report pattern
> is a bit spikey, in that kernels that get picked up by popular
> distributions get more reports than those that don't (no big surprise,
> those just have a much larger user base), but otherwise there's no up
> or down trend to be seen there.
>
Majority of old bugs that are still open are of "hard to reproduce"
category. That means you are not very likely to hit them. Those can
be: legacy devices failing, relatively rare hardware, code clean-ups
etc. You can't find really critical long standing bugs in the old
backlog. It doesn't mean old bugs don't get fixed, rather get less
priority that severe bugs and regressions.
With emphasys that was put on cleaning up bugs by Andrew and other
developers, bugs are taken even more seriously than before. New bugs,
regressions are being tracked aggressively, so they don't stay open
for long time. You can search for Rafael's regression reports and
sample time line of a reported regression: they are short lived bugs.
Overall, each kernel release has great deal of improvement over older
ones, by nature of Linux. Many distros now tend to stay as close with
new releases of main line as possible. This seems to be the best way
to get all the bug fixes, optimizations, and features.
Regards,
--Natalie
>
>>
>> > Thanks!
>> >
>> > Sincerely,
>> > Bosko
>>
>> cu
>> Adrian
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2008-05-22 15:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 12:28 Bosko Radivojevic
2008-05-22 14:41 ` Adrian Bunk
2008-05-22 14:51 ` Arjan van de Ven
2008-05-22 15:47 ` Natalie Protasevich [this message]
2008-05-22 15:54 ` Adrian Bunk
2008-05-22 16:20 ` Natalie Protasevich
2008-05-22 16:50 ` Adrian Bunk
2008-05-22 17:08 ` Natalie Protasevich
2008-05-22 17:33 ` Adrian Bunk
2008-05-22 17:51 ` Natalie Protasevich
2008-05-22 18:11 ` Adrian Bunk
2008-05-22 22:18 ` Arjan van de Ven
2008-05-23 9:09 ` Adrian Bunk
2008-05-23 14:11 ` Arjan van de Ven
2008-05-23 16:50 ` Adrian Bunk
2008-05-23 18:29 ` Arjan van de Ven
2008-05-23 20:31 ` Adrian Bunk
2008-05-26 17:05 ` Dave Jones
2008-05-23 10:35 ` James Courtier-Dutton
2008-05-23 15:35 ` Takashi Iwai
2008-05-22 16:22 ` Stefan Richter
2008-05-22 16:38 ` Bart Van Assche
2008-05-22 17:09 ` Adrian Bunk
2008-05-22 17:45 ` Stefan Richter
2008-05-22 19:17 ` Adrian Bunk
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=32209efe0805220847h5495fd7ctf1c3b9fdd387ec2d@mail.gmail.com \
--to=protasnb@gmail.com \
--cc=arjan@infradead.org \
--cc=bosko.radivojevic@gmail.com \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome