|
|
Subscribe / Log in / New account

Bugs per commit

Bugs per commit

Posted Sep 30, 2025 14:43 UTC (Tue) by iabervon (subscriber, #722)
Parent article: Development statistics for 6.17

It looks like the commits that introduce the most bugs are mostly the ones that add new drivers, which makes sense in that they also introduce more new code, in general, and also generally don't have any tests for corner cases the author didn't think of (unlike changes that often have tests that someone wrote previously). And they generally can't cause regressions (other than hardware users didn't need waking up and causing problems), so the bugs take longer to notice.

You could reasonably say that the addition of the xe driver broke down the single big bug (of the hardware being entirely unsupported) into a lot of smaller, harder-to-trigger bugs and fixed a lot of test cases while leaving a relatively small number of test cases unaddressed.


to post comments

Bugs per commit

Posted Sep 30, 2025 16:29 UTC (Tue) by npws (subscriber, #168248) [Link]

It seems to derive any conclusions from the bug numbers, they at least need to be put in relation to the LOC of the commit that introduced them, or some related metric. It is hardly a surprise that 10000 lines of code contain more bugs then 10 lines of code.


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds