lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <AANLkTikWb43Vfs4s9ux2jBaLRtMSg+pZ7KEoev3pXMPB@mail.gmail.com>
Date:	Sat, 11 Sep 2010 20:11:34 +0200
From:	Jan III Sobieski <jan3sobi3ski@...il.com>
To:	Florian Mickler <florian@...kler.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: 2458 days of Linux development - some stats and thoughts

2010/9/11 Florian Mickler <florian@...kler.org>:
> On Sat, 11 Sep 2010 00:04:18 +0200
> Jan III Sobieski <jan3sobi3ski@...il.com> wrote:
>
>> I added regressions stats - total number of regressions for each
>> kernel and number of regressions not fixed yet. It is interesting that
>> the number of not fixed regressions is really low.
>>
>
> What should I do with these numbers, when I don't know
> how they are created? What do they signify? What is their relevance?
> What uncertainty is connected to these numbers? What follows? Why are
> they created? How are they related?

This is just simple stat based on diffs. For example - 2.6.32


32	1096601	534042	315020	228772	781581	305270	1086851	543792	1630643	85
 	8	882149	463400	1345549	82,52%	160	28


32 - version
1096601 - insertions for whole 2.6.32 patch
534042 - deletions for whole 2.6.32 patch
315020 - insertions in drivers/staging dir
228772 - deletions in drivers/staging dir
781581 - insertions in base (without staging - most people doesn't use
it and doesn't care about this code - it's just a noise in diff's)
305270 - deletions in base
1086851 - sum of base insertions and deletions
543792 - sum of staging insertions and deletions
1630643 - sum of insertions and deletions in whole patch
85 - how many days took to develop this kernel
8 - how many rc's was produced
882149 - insertions from latest -next tree for 2.6.32
463400 - deletions from latest -next tree for 2.6.32
1345549 - sum of above for latest -next tree for 2.6.32
82,52% - how many changed lines was tested in -next tree
160	- total number of regressions tracked for 2.6.32
28 - regressions that are not fixed yet

I see a trend in the latest kernels (since 2.6.32) to minimize sum of
changes in base (without drivers/staging) - average is less than
1086851 lines changed and regressions dropped down bellow 160 for each
release. From 2.6.24 to 2.6.31 there were a lot more changes in base
and total number of regressions for each version was above 160 (with
one exception).

You can also see some dependency between number of regressions and
percent of changes coveraged in -next tree.

But this is just random stats - you can see whatever you want ;)

>
> Cheers,
> Flo
>

-- 
Jan III Sobieski
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ