Linux kernel development

Linux kernel development
Name	Linux kernel
Developer	Linus Torvalds, Linux Foundation, contributors
Released	1991
Programming language	C, Assembly language
Operating system	Linux
License	GNU General Public License

Linux kernel development Linux kernel development is the collaborative process that produces the core kernel used by distributions such as Debian, Ubuntu, Red Hat Enterprise Linux, Fedora, SUSE Linux Enterprise Server and devices from companies like Google, IBM, Intel Corporation and ARM Ltd.. It involves individuals and organizations including maintainers, contributors, and corporate engineering teams coordinating through systems created by figures like Linus Torvalds and institutions such as the Linux Foundation. The project interacts with related efforts like GNU Project, BusyBox, systemd and standards bodies such as IEEE and IETF.

History

The origins trace to work by Linus Torvalds in 1991 following influences from projects like MINIX and historical systems such as Unix. Early community organization involved mailing lists and patch submissions similar to practices in the FreeBSD and NetBSD communities. Growth accelerated through corporate involvement from companies including Red Hat, SUSE, IBM, Intel Corporation and Novell, and through landmark events like the creation of the Linux Foundation and initiatives such as the Open Source Initiative. Major milestones include the adoption of the GNU General Public License, the move to a distributed development model with Git and the evolution of subsystems inspired by work at institutions like University of Helsinki and labs at Bell Labs.

Development process and governance

Governance centers on maintainers, subsystem leads, and the benevolent dictator role of Linus Torvalds with stewardship from the Linux Foundation. Decision-making uses formal mechanisms like maintainers trees, the role of subsystem maintainers, and developer interactions on mailing lists such as Linux Kernel Mailing List. Corporate governance is visible through collaborations with entities like Red Hat, Intel Corporation, Google and Samsung Electronics. Licensing, code of conduct development and copyright assignment involve legal frameworks referencing the GNU General Public License and practices influenced by organizations such as the Free Software Foundation.

Architecture and subsystems

The kernel's modular design organizes code into subsystems including Virtual Memory, Networking, Device drivers, File system and Process scheduling derived from long research traditions at institutions like MIT, Carnegie Mellon University and University of California, Berkeley. Architecture support spans platforms such as x86 architecture, ARM architecture, PowerPC and RISC-V, with platform-specific code coordinated by maintainers and companies like AMD and NVIDIA. Subsystems interact with projects such as udev, systemd, GRUB and standards efforts like POSIX to ensure compatibility across distributions like Debian and Arch Linux.

Contribution workflow and tools

Contributors use tools and services including Git, Patchwork, Gerrit, and the Linux Kernel Mailing List for patch submission, review, and integration. Development follows a workflow with forks, pull requests in hosting services such as GitHub and patch series sent via email; maintainers curate trees merged by top-level integrators, ultimately coordinated by Linus Torvalds. Continuous integration and testing use infrastructures provided by companies like Google and projects including KernelCI, Test Robot and hardware labs from vendors such as Intel Corporation and Linaro.

Release cycle and versioning

Releases follow a cadence established by the core development community with stable, long-term support (LTS) kernels maintained by individuals and organizations such as Greg Kroah-Hartman and the Linux Foundation. Versioning evolved from numeric schemes to current practices where odd/even numbering gave way to semantic-style identifiers; distributions like Ubuntu and Fedora package specific kernel versions according to their release policies. Release events are coordinated around merge windows, stabilization phases and tag points managed by maintainers and announced on channels including the Linux Kernel Mailing List.

Security and maintenance

Security management involves coordinated disclosure, stable branch backports, and responses by security teams at enterprises like Red Hat, Canonical and SUSE. Vulnerability tracking and CVE handling interact with databases managed by entities such as MITRE, and coordinated responses reference standards from NIST and incident processes used by vendors like IBM. Maintenance activities include backporting, regression testing with infrastructures like KernelCI and stewardship by LTS maintainers and corporate security teams.

Community and organizations

The ecosystem comprises individual developers, companies, foundations and user communities including Linux Foundation, Free Software Foundation, distribution projects like Debian and Arch Linux, and companies such as Red Hat, Canonical, SUSE, Intel Corporation, Google and IBM. Events and conferences important to the community include LinuxCon, Kernel Summit, FOSDEM and regional meetups organized by local groups like Linux User Group chapters. Collaborative programs, funding and training are supported by organizations including the Linux Foundation and academic partners at institutions such as MIT, Stanford University and ETH Zurich.

Category:Operating system kernels