Nicolas Palix,
Gaël Thomas,
Suman Saha,
Christophe Calvès,
Julia Lawall,
and Gilles Muller.
Faults in Linux: Ten Years Later.
In Sixteenth International Conference on Architectural Support for Programming Languages and Operating Systems (ASPLOS 2011),
Newport Beach, California, USA,
pages 305-318,
March 2011.
ISBN: 978-1-4503-0266-1.
Keyword(s): Linux,
Coccinelle,
Herodotos.
Abstract: |
In 2001, Chou et al. published a study of faults found by applying a static analyzer to Linux versions 1.0 through 2.4.1. A major result of their work was that the drivers directory contained up to 7 times more of certain kinds of faults than other directories. This result inspired a number of development and research efforts on improving the reliability of driver code. Today, however, Linux is used in a much wider range of environments, provides a much wider range of services, and has adopted a new development and release model. What has been the impact of these changes on code quality? Are drivers still a major problem? To answer these questions, we have attempted to transport, based on the information provided, the experiments of Chou et al. to Linux versions 2.6.0 to 2.6.33, released between late 2003 and early 2010. We find that even if Linux has more than doubled in size during this period, the number of faults per line of code has been decreasing. And, even though drivers still accounts for a large part of the kernel code and contains the most faults, its fault rate is now below that of other directories, such as arch (HAL) and fs (file systems). Such information can guide further development and research efforts. To enable others to continually update the results as Linux evolves, we define our experimental protocol and make our checkers and results available in a public archive. |
@INPROCEEDINGS{palix:asplos11,
ADDRESS = {Newport Beach, California, USA},
AUTHOR = {Nicolas Palix and Gaël Thomas and Suman Saha and Christophe Calvès and Julia Lawall and Gilles Muller},
BOOKTITLE = {Sixteenth International Conference on Architectural Support for Programming Languages and Operating Systems (ASPLOS 2011)},
OPTEDITOR = {},
MONTH = {March},
OPTNOTE = {},
OPTNUMBER = {},
OPTORGANIZATION = {},
PAGES = {305--318},
OPTPUBLISHER = {},
OPTSERIES = {},
TITLE = {Faults in Linux: Ten Years Later},
OPTVOLUME = {},
YEAR = {2011},
ABSTRACT = { In 2001, Chou et al. published a study of faults found by applying a static analyzer to Linux versions 1.0 through 2.4.1. A major result of their work was that the drivers directory contained up to 7 times more of certain kinds of faults than other directories. This result inspired a number of development and research efforts on improving the reliability of driver code. Today, however, Linux is used in a much wider range of environments, provides a much wider range of services, and has adopted a new development and release model. What has been the impact of these changes on code quality? Are drivers still a major problem? To answer these questions, we have attempted to transport, based on the information provided, the experiments of Chou et al. to Linux versions 2.6.0 to 2.6.33, released between late 2003 and early 2010. We find that even if Linux has more than doubled in size during this period, the number of faults per line of code has been decreasing. And, even though drivers still accounts for a large part of the kernel code and contains the most faults, its fault rate is now below that of other directories, such as arch (HAL) and fs (file systems). Such information can guide further development and research efforts. To enable others to continually update the results as Linux evolves, we define our experimental protocol and make our checkers and results available in a public archive. },
DOI = {10.1145/1950365.1950401},
ISBN = {978-1-4503-0266-1},
OPTISSN = {},
KEYWORDS = {Linux, Coccinelle, Herodotos},
URL = {http://doi.acm.org/10.1145/1950365.1950401},
OPTURL-PUBLISHER = {},
PDF = {http://proton.inrialpes.fr/~npalix/papers/asplos11-palix.pdf}
}