DOCSLIB.ORG

Keeping the Linux Kernel Honest Testing Kernel.Org Kernels

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Keeping the Linux Kernel Honest Testing Kernel.Org Kernels Keeping the Linux Kernel Honest Testing Kernel.org kernels Kamalesh Babulal Balbir Singh IBM IBM [email protected] [email protected] Abstract 10000000 9500000 TM 9000000 The Linux Kernel release cycle has been short v2.6.24 v2.6.23 with various intermediate releases and with the lack 8500000 v2.6.22 of a separate kernel development tree. There have v2.6.21 8000000 v2.6.20 v2.6.19 been many challenges with this rapid development v2.6.18 Lines of Code 7500000 v2.6.17 v2.6.16 such as early bug reporting, regression tracking, func- v2.6.15 v2.6.14 tional/performance testing, and test coverage by dif- 7000000 v2.6.13 v2.6.12 v2.6.11 ferent individuals and projects. Many kernel develop- 6500000 ers/testers have been working to keep the quality of the 6000000 0 100 200 300 400 500 600 700 800 900 1000 1100 1200 1300 kernel high, by testing as many possible subsystems as Days of Development they can. Figure 1: Size of the kernel with every release In this paper, we present our kernel testing methodology, infrastructure, and results used for the v2.6 kernels. We summarize the bug reporting statistics based on the dif- • Testing on wide range of architectures and plat- ferent kernel subsystems, trends, and observations. We forms, will also present code coverage analysis by subsystem • Regressions carried from previous release, for different test suites. • Different development trees, and 1 Introduction • Various configurations and boot options to be tested. The Linux kernel has been growing with every release as a result of the sheer number of new features being In Section 2 we briefly explain the challenges. Section 3 merged. These changes are being released at a very high outlines our methodology to meet the challenges. Sec- rate, with each release containing a very large number tion 4 presents the results of code coverage analysis, in- of changes and new features. The time latency at which cluding the fault injection coverage results for the stan- these changes are made is very short between every re- dard test cases and we discuss our future plans in Sec- lease cycle. All of this is occurring across many dis- tion 5. parate hardware architectures. This presents unique problems for a tester who must 2 Challenges take all of the following into account: 2.1 Different Trees • Lines of code added, • Time interval between each release, In the past, Linux kernel development had separate de- velopment and stable trees. The stable trees had an even • Number of intermediate releases, number and the development trees had an odd number • 19 • 20 • Keeping the Linux Kernel Honest as their second release number. As an example 2.5 was a regular basis would allow the development and stable development release, while 2.4 was stable release. With releases to be based on the -next tree in the future (re- the 2.6 kernel development, there are no separate devel- fer to [5] for more information on kernel trees). opment and stable trees. All the development is based upon the current stable tree and once the current devel- opment tree is marked as stable, it is released as the next mainline release. maintainers tree -mm -stable There are intermediate development releases between major releases of a 2.6 kernels, each having its own -rc1 distributions significance. Figure 2 shows the different development trees and the flow of patches from development trees to the mainline kernel. -gits The -stable tree contains critical fixes for security -rcN release -next users problems or significant regressions identified for the mainline tree it is based upon. Once the mainline tree is released, the developers start contributing to the new mainline release features to be included in the next release. The new fea- tures are accepted for the inclusion during the first two weeks of development following the mainline release. Bug Fixes Features Rebase Releases After two weeks the merge window closes and the ker- nel is in feature freeze; no further features will be ac- cepted into this release. This is released as -rc1. After Figure 2: Linux Kernel Development Cycle -rc1 the features are tested well and stabilized. During this period roughly weekly release candidates, -rc, are produced, as well as intermediate snapshots of Linus’s 2.2 Release Frequency git tree. Testing is essential to deliver high quality software and The -rc releases are a set of patches for the bug fixes testing every phase of development is important if we and other important security fixes, based on the previous are to catch bugs early. This is especially true for -rc release. For example, 2.6.25-rc3 will have the fixes projects like Linux where the source is growing by for the bugs identified in 2.6.25-rc2. 2.32% [1] with every release, as represented in Figure 1. In addition to the mainline releases, we have a number These numbers are pretty high for any project. Starting of testing trees for less stable features, as well as sub- from 2.6 kernel development series, there is no sepa- system specific trees. The -mm tree has experimental rate stable and development tree, which means that more patches and critical fixes that are planned to be pushed code is being added and it needs to be tested thoroughly. to the mainline kernel. For a new feature it is recom- Bugs caught and fixed early in the cycle helps to main- mended that it be tested in -mm, since that tree under- tain the kernel quality by: goes rigorous testing, which in-turn helps in stabilizing the feature. -mm is rebased often to development re- leases to test the patch set against the development tree. • Providing a pleasant user experience, The -next release was introduced with the 2.6.24 • Avoiding building on top of buggy code, and development series. The -next tree has the patch • Easier debugging, since the code is fresh in the au- changesets from different maintainers, intended to be thors mind. merged into the next release. Changesets are rebased to the current development tree, which helps to resolve the merge conflicts and bugs before they get introduced The stable kernel releases are made approximately ev- in the next release. Resolving the conflicts and bugs on ery 2-3 months, during which time an average of 3.18 2008 Linux Symposium, Volume One • 21 v2.6 kernels • Regression Testing, versions .20 .21 .22 .23 .24 Total stable 22 8 20 18 5 73 • Stress Testing, stable-git 16 18 18 26 22 100 • Performance Testing, and stable-mm 2 2 0 1 1 4 stable-mm • Functional Testing. +hotfixe(s) 0 0 0 3 6 9 rc 7 7 11 8 8 41 These efforts are not being captured completely because rc-git 59 52 57 70 47 285 most of these efforts are not visible. We will not be able rc-mm 12 6 10 7 4 41 to account for any testing done unless it is being pub- rc-mm lished or shared. Many features are accepted into the +hotfixe(s) 0 10 18 14 3 45 mainline after stringent code reviews and ample testing next 0 0 0 0 35 35 in the development releases. But not many developers Total 118 103 134 147 131 633 provide the test cases or guidelines to test their func- tionality even though it is in the interest of developers to Table 1: Summary of releases between kernel versions keep the quality of their code high. Over the years there have been many test projects and changes are being accepted every hour. This has been suites with a primary focus to improve the quality of the trend for the past 1 1 years. Linux. They are constantly undergoing lots of changes 2 between every release. They have been adding new test Table 1 shows the data of various intermediate releases cases to test the new features getting merged into the 1 kernel, but the updating is not fast enough to catch those made for past 1 2 years. These incremental changes to the kernel source ensure that any code changes made early bugs and for some features we do not have test to the kernel are well tested before they accepted into cases available. mainline. Any person who is interested in testing the kernel has no With the average of 126 kernels (refer to Table 1) be- single, nor even a small number, of test projects which ing released between two sequential major releases, we can cover most of the kernel subsystems. We do have have at least one kernel per day being released. Devel- a large number of test projects, but each is independent opers end up limiting their testing to unit testing for the requiring installation and configuration; the test setup is changes they make and start concentrating on new de- a huge effort for a tester. Not all the testers have the velopment. It is not practical for most of the developers harness infrastructure in place for testing due to the lim- to test their changes across all architectures supported itations of the hardware they own. by Linux. A significant amount of testing is being done Most of the test projects act at best as regression, stress, by others from the community, which includes testers, performance test suites, or combinations thereof, but we developers, and vendors (including distribution compa- do not have tests which can be used for functional test- nies). ing of the new features being merged into the kernel.
Load more

Recommended publications
  • Redhawk Linux User's Guide
    Linux® User’s Guide 0898004-520 May 2007 Copyright 2007 by Concurrent Computer Corporation. All rights reserved. This publication or any part thereof is intended for use with Concurrent products by Concurrent personnel, customers, and end–users. It may not be reproduced in any form without the written permission of the publisher. The information contained in this document is believed to be correct at the time of publication. It is subject to change without notice. Concurrent makes no warranties, expressed or implied, concerning the information contained in this document. To report an error or comment on a specific portion of the manual, photocopy the page in question and mark the correction or comment on the copy. Mail the copy (and any additional comments) to Concurrent Computer Corporation, 2881 Gateway Drive, Pompano Beach, Florida, 33069. Mark the envelope “Attention: Publications Department.” This publication may not be reproduced for any other reason in any form without written permission of the publisher. Concurrent Computer Corporation and its logo are registered trademarks of Concurrent Computer Corporation. All other Concurrent product names are trademarks of Concurrent while all other product names are trademarks or registered trademarks of their respective owners. Linux® is used pursuant to a sublicense from the Linux Mark Institute. Printed in U. S. A. Revision History: Date Level Effective With August 2002 000 RedHawk Linux Release 1.1 September 2002 100 RedHawk Linux Release 1.1 December 2002 200 RedHawk Linux Release 1.2 April 2003 300 RedHawk Linux Release 1.3, 1.4 December 2003 400 RedHawk Linux Release 2.0 March 2004 410 RedHawk Linux Release 2.1 July 2004 420 RedHawk Linux Release 2.2 May 2005 430 RedHawk Linux Release 2.3 March 2006 500 RedHawk Linux Release 4.1 May 2006 510 RedHawk Linux Release 4.1 May 2007 520 RedHawk Linux Release 4.2 Preface Scope of Manual This manual consists of three parts.
    [Show full text]
  • Kshot: Live Kernel Patching with SMM and SGX
    KShot: Live Kernel Patching with SMM and SGX Lei Zhou∗y, Fengwei Zhang∗, Jinghui Liaoz, Zhengyu Ning∗, Jidong Xiaox Kevin Leach{, Westley Weimer{ and Guojun Wangk ∗Department of Computer Science and Engineering, Southern University of Science and Technology, Shenzhen, China, zhoul2019,zhangfw,ningzy2019 @sustech.edu.cn f g ySchool of Computer Science and Engineering, Central South University, Changsha, China zDepartment of Computer Science, Wayne State University, Detroit, USA, [email protected] xDepartment of Computer Science, Boise State University, Boise, USA, [email protected] Department of Computer Science and Engineering, University of Michigan, Ann Arbor, USA, kjleach,weimerw @umich.edu { f g kSchool of Computer Science and Cyber Engineering, Guangzhou University, Guangzhou, China, [email protected] Abstract—Live kernel patching is an increasingly common kernel vulnerabilities also merit patching. Organizations often trend in operating system distributions, enabling dynamic up- use rolling upgrades [3], [6], in which patches are designed dates to include new features or to fix vulnerabilities without to affect small subsystems that minimize unplanned whole- having to reboot the system. Patching the kernel at runtime lowers downtime and reduces the loss of useful state from running system downtime, to update and patch whole server systems. applications. However, existing kernel live patching techniques However, rolling upgrades do not altogether obviate the need (1) rely on specific support from the target operating system, to restart software or reboot systems; instead, dynamic hot and (2) admit patch failures resulting from kernel faults. We patching (live patching) approaches [7]–[9] aim to apply present KSHOT, a kernel live patching mechanism based on patches to running software without having to restart it.
    [Show full text]
  • Red Hat Enterprise Linux 7 Kernel Administration Guide
    Red Hat Enterprise Linux 7 Kernel Administration Guide Examples of Tasks for Managing the Kernel Last Updated: 2018-05-21 Red Hat Enterprise Linux 7 Kernel Administration Guide Examples of Tasks for Managing the Kernel Marie Dolezelova Red Hat Customer Content Services [email protected] Mark Flitter Red Hat Customer Content Services Douglas Silas Red Hat Customer Content Services Eliska Slobodova Red Hat Customer Content Services Jaromir Hradilek Red Hat Customer Content Services Maxim Svistunov Red Hat Customer Content Services Robert Krátký Red Hat Customer Content Services Stephen Wadeley Red Hat Customer Content Services Florian Nadge Red Hat Customer Content Services Legal Notice Copyright © 2018 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates.
    [Show full text]
  • Red Hat Enterprise Linux 8 Managing, Monitoring and Updating the Kernel
    Red Hat Enterprise Linux 8 Managing, monitoring and updating the kernel A guide to managing the Linux kernel on Red Hat Enterprise Linux 8 Last Updated: 2019-11-05 Red Hat Enterprise Linux 8 Managing, monitoring and updating the kernel A guide to managing the Linux kernel on Red Hat Enterprise Linux 8 Legal Notice Copyright © 2019 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
    [Show full text]
  • Understanding the Linux Virtual Memory Manager
    1 Understanding The Linux Virtual Memory Manager Mel Gorman 15th February 2004 Contents List of Figures 5 List of Tables 7 Acknowledgements 9 1 Introduction 12 1.1 General Kernel Literature . 13 1.2 Thesis Overview . 14 1.3 Typographic Conventions . 14 1.4 About this Document . 14 1.5 Companion CD . 15 2 Code Management 17 2.1 Managing the Source . 17 2.2 Getting Started . 23 2.3 Submitting Work . 24 3 Describing Physical Memory 26 3.1 Nodes . 27 3.2 Zones . 29 3.3 Pages . 31 3.4 High Memory . 33 4 Page Table Management 36 4.1 Describing the Page Directory . 37 4.2 Describing a Page Table Entry . 38 4.3 Using Page Table Entries . 39 4.4 Translating and Setting Page Table Entries . 42 4.5 Allocating and Freeing Page Tables . 42 4.6 Kernel Page Tables . 43 4.7 Mapping addresses to struct pages .................. 44 5 Process Address Space 47 5.1 Linear Address Space . 48 5.2 Managing the Address Space . 49 2 CONTENTS 3 5.3 Process Address Space Descriptor . 50 5.4 Memory Regions . 55 5.5 Exception Handling . 70 5.6 Page Faulting . 71 5.7 Copying To/From Userspace . 77 6 Boot Memory Allocator 80 6.1 Representing the Boot Map . 81 6.2 Initialising the Boot Memory Allocator . 81 6.3 Allocating Memory . 83 6.4 Freeing Memory . 85 6.5 Retiring the Boot Memory Allocator . 85 7 Physical Page Allocation 90 7.1 Managing Free Blocks . 90 7.2 Allocating Pages . 91 7.3 Free Pages .
    [Show full text]
  • Open Source Software License Information
    Open Source Software license information This document contains an open source software license information for the product VACUU·SELECT. The product VACUU·SELECT contains open source components which are licensed under the applicable open source licenses. The applicable open source licenses are listed below. The open source software licenses are granted by the respective right holders directly. The open source licenses prevail all other license information with regard to the respective open source software components contained in the product. Modifications of our programs which are linked to LGPL libraries are permitted for the customer's own use and reverse engineering for debugging such modifications. However, forwarding the information acquired during reverse engineering or debugging to third parties is prohibited. Furthermore, it is prohibited to distribute modified versions of our programs. In any case, the warranty for the product VACUU·SELECT will expire, as long as the customer cannot prove that the defect would also occur without these modification. WARRANTY DISCLAIMER THE OPEN SOURCE SOFTWARE IN THIS PRODUCT IS DISTRIBUTED IN THE HOPE THAT IT WILL BE USEFUL, BUT WITHOUT ANY WARRANTY, WITHOUT EVEN THE IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. See the applicable licenses for more details. Written offer This product VACUU·SELECT contains software components that are licensed by the holder of the rights as free software, or Open Source software, under GNU General Public License, Versions 2 and 3, or GNU Lesser General Public License, Versions 2.1, or GNU Library General Public License, Version 2, respectively. The source code for these software components can be obtained from us on a data carrier (e.g.
    [Show full text]
  • Controlling Tracepoints AMD Performance Counting Clearer
    PROgRAMMIng Kernel News zack’s kernel news m68k Revitalized Under git Controlling Tracepoints nilfs2 Headed For Inclusion Geert Uytterhoeven announced a new git Steven Rostedt has posted a patch to Ryusuke Konishi has submitted nilfs2 for repository for the m68k Linux port, replac- ftrace, providing a simple interface for inclusion in the main kernel tree. Up to ing a defunct CVS repository. He also users to enable and disable any trace- now, it has lived in Andrew Morton’s posted a patch to add a make install com- point that already exists in the kernel. -mm tree. As Andrew has said, Konishi’s pilation target for the m68k build and The new /debug/tracing/available_ efforts have been quite impressive, and posted several other m68k updates as well. events file lists all tracepoints available he’s offered him some advice for further for tracking, whereas the /debug/tracing/ development. Andrew strongly supports MSI HOWTO Rewrite set_event can be modified to list the the filesystem and plans to send the Matthew Wilcox has rewritten the MSI events you want to enable or disable. patches along to Linus Torvalds in the HOWTO, the first major rewrite since very near future, barring serious objec- 2004. MSI (or Message Signaled Inter- AMD Performance Counting tion from other kernel hackers. nilfs2 rupts) provide PCI devices with an alter- Jaswinder Singh Rajput posted some provides full versioning within the file- native to traditional interrupts that re- patches to implement performance system, including continuous snapshot- quire the existence of a hardware pin on counting for AMD K7 (and later) proces- ting and access to older snapshots.
    [Show full text]
  • Status and Direction of Kernel Development Andrew Morton
    Status and Direction of Kernel Development Andrew Morton <[email protected]> <[email protected]> Linux Foundation Japan Linux Symposium 2008 July 2008 Page 1 of 18 Overview ● Process – The linux-next tree – Embedded development – X86 – Realtime ● Technology – Filesystems – Memory management – Hardware virtualisation (Xen/vmware/KVM) – OS virtualisation (containers) – RAS – AIO – Tracing Page 2 of 18 The “linux-next” tree ● A GIT tree operated by Stephen Rothwell – Merges together 104 subsystem development trees – This represents 85% of the changes in Linux. The remaining 15% is in the -mm tree. ● I will soon feed most of the -mm tree into linux-next so we get close to 100% Page 3 of 18 Why “linux-next” exists ● To reduce the amount of breakage which occurs during the 2.6.x-rc1 merge window. – because it gets additional testing ● To provide an integration tree in which the various subsystem changes can be tested together ● To help persuade subsystem developers to not make conflicting changes – I was seeing a lot of this happening. The prominence of linux-next makes people more careful about what they merge. ● To take the "subsystem tree integration" function out of my hands – I wasn't doing it very well and it was getting harder and harder Page 4 of 18 “linux-next” status ● It is going well - perhaps better than I had expected ● It still isn't receiving as much testing as I would like. ● There is some testing by "testers" but few if any "developers" appear to be testing linux-next. ● This is bad because individual developers are now testing their changes in the 2.6.x environment, but that code is destined to be integrated into 2.6.x+1.
    [Show full text]
  • Fully Automated Testing of the Linux Kernel
    Fully Automated Testing of the Linux Kernel Martin Bligh Andy P. Whitcroft Google Inc. IBM Corp. [email protected] [email protected] Abstract formance regressions and trends, adding sta- tistical analysis. A broad spectrum of tests are necessary—boot testing, regression, func- Some changes in the 2.6 development process tion, performance, and stress testing; from disk have made fully automated testing vital to the intensive to compute intensive to network in- ongoing stability of Linux R . The pace of de- tensive loads. A fully automated test harness velopment is constantly increasing, with a rate also empowers other other techniques that are of change that dwarfs most projects. The lack impractical when testing manually, in order of a separate 2.7 development kernel means that to make debugging and problem identification we are feeding change more quickly and di- easier. These include automated binary chop rectly into the main stable tree. Moreover, the search amongst thousands of patches to weed breadth of hardware types that people are run- out dysfunctional changes. ning Linux on is staggering. Therefore it is vi- tal that we catch at least a subset of introduced In order to run all of these tests, and collate the bugs earlier on in the development cycle, and results from multiple contributors, we need an keep up the quality of the 2.6 kernel tree. open-source client test harness to enable shar- Given a fully automated test system, we can ing of tests. We also need a consistent output run a broad spectrum of tests with high fre- format in order to allow the results to be col- quency, and find problems soon after they are lated, analysed and fed back to the community introduced; this means that the issue is still effectively, and we need the ability to “pass” fresh in the developers mind, and the offending the reproduction of issues from test harness to patch is much more easily removed (not buried the developer.
    [Show full text]
  • How to Participate in the Linux Community a Guide to the Kernel Development Process
    How to Participate in the Linux Community A Guide To The Kernel Development Process by Jonathan Corbet, [email protected] The purpose of this document is to help developers (and their managers) work with the development community with a minimum of frustration. It is an attempt to document how this community works in a way which is accessible to those who are not intimately familiar with Linux kernel development (or, indeed, free software development in general). While there is some technical material here, this is very much a process- oriented discussion which does not require a deep knowledge of kernel programming to understand. August 2008 1.1: Executive Summary 1.2: What This Document Is About The rest of this section covers the scope of the kernel development The Linux kernel, at over 6 million lines of code and well over 1000 process and the kinds of frustrations that developers and their active contributors, is one of the largest and most active free software employers can encounter there. There are a great many reasons projects in existence. Since its humble beginning in 1991, this kernel why kernel code should be merged into the official (“mainline”) has evolved into a best-of-breed operating system component which kernel, including automatic availability to users, community support runs on pocket-sized digital music players, desktop PCs, the largest in many forms, and the ability to influence the direction of kernel supercomputers in existence, and all types of systems in between. It development. Code contributed to the Linux kernel must be made is a robust, efficient, and scalable solution for almost any situation.
    [Show full text]
  • Hacking the Linux Kernel for Fun and Profit
    Hacking the Linux Kernel for Fun and Profit James Bottomley Hansen Partnership, Inc. 5 April 2008 1 Introduction • The Linux Kernel is becoming an increasingly complex place – The number of “core subsystem” maintainers is growing – The number of supported features is growing – The rate of change of code is also (currently) growing • Often difficult to understand what you’re changing. • Even more difficult to work out what the correct way to change it is. • However, the kernel has a basic need for talented and motivated contributors 2 Agenda 1. OK, I understand the Fun Part, where’s the Profit? 2. Why you should contribute code to the Kernel (and why your Employer should pay you to do it). 3. Why the Kernel needs you to contribute. 4. Why it isn’t as simple as it sounds 5. Where to go to get help 3 Where’s the Money 1. Current total investment in Linux up to 2008: $2BN 2. Annual Income derived from Linux in 2007: $2BN 3. So, there’s a lot of money floating around. 4. The problem is, not much of it goes directly to kernel developers. 5. Open Source is about Code not Business Models 6. However Good Business models make money off Open Source 7. Moral: If you want to get really rich, start a company. 4 Indirect Economic Benefits • Most open source projects hire the top contributors in their area. • Even if that’s not you, a large number of recruiters use open source mailing lists as a tool. • Everything you do in open source is on show and easily searchable – Recruiters know this.
    [Show full text]
  • Building a Robust Linux Kernel Piggybacking the Linux Test Project
    Building a Robust Linux Kernel piggybacking The Linux Test Project Subrata Modak & Balbir Singh, Linux Technology Center, IBM, India OLS 2008 Dated 25/07/2008 Linux is a registered trademark of Linus Torvalds. Agenda ● Introduction – some background checks ● Addressing some Criticism ● Breathing a new life into LTP ● Kernel code coverage statistics ● Role of LTP in testing Linux ● Early & Effective testing ● Simplest way to write an LTP test case ● Future Plans ● Conclusion 2 © 2008 IBM Corporation Everybody is happy, and... they should be ● Linux Kernel is growing at a rapid rate and runs across numerous architectures...neighbor´s envy – ownerś pride Mission Critical... ● Keeping the kernel reliable, stable & robust Somebody doing the Job...?? ● Yes, The Linux Test Project ● It was established to meet the very goals stated above 3 © 2008 IBM Corporation Beware to ignore testing...!! you will end up in ● Frequent crashes ● Frequent Updates ● Unhappy users 4 © 2008 IBM Corporation Introduction – some background checks ● First created by SGI in 2001 - brought organized and automated testing to Linux for first time ● Primary goal: provide a test suite that can validate the robustness, stability & reliability of Linux kernel ● A functional and regression test suite that allows to do stress testing as well ● No. of tests at kernel 2.3 was mere 100 ● Today at 2.6.25 , it stands at 3000+ and growing... ● Tests numerous kernel features, namely syscalls, MM, IPC, I/O, device drivers, FS, Networking, etc ● What´s the code written in ??... 95% in
    [Show full text]