Linux kernel

The Linux kernel, developed by contributors worldwide, is a free and open-source, monolithic, modular, Unix-like operating system kernel.
It is deployed on a wide variety of computing systems, such as embedded devices, mobile devices, personal computers, servers, mainframes, and supercomputers.
The Linux kernel was conceived and created in 1991 by Linus Torvalds for his personal computer and with no cross-platform intentions, but has since ported to a wide range of computer architectures. Notwithstanding this, the Linux kernel is highly optimized with the use of architecture specific instructions, therefore portability isn't as easy as it is with other kernels.
Linux was soon adopted as the kernel for the GNU Operating System, which was created as an open source and free software, and based on UNIX as a by-product of the fallout of the Unix wars. Since then it has spawned a plethora of operating system distributions, commonly also called Linux, although, formally, the term "Linux" refers only to the kernel.
Day-to-day development discussions take place on the Linux kernel mailing list. Linux as a whole, as it is clearly stated in the COPYING file, is released under the GNU General Public License version 2, but it also contains several files under other compatible licenses and an ad hoc exemption for the User-space API header files.
The Linux ABI between the kernel and the user space has four degrees of stability, however the system calls are expected to never change in order to not break the userspace programs that rely on them. As far as in-kernel APIs are regarded, there's no guarantee of stability. Device drivers included in the mainline Linux must be kept updated by their maintainers in order to stay at pace with the kernel evolution. Furthermore, the interface between the kernel and loadable kernel modules, unlike in many other kernels, is not meant to be stable by design.


In April 1991, Linus Torvalds, at the time a 21-year-old computer science student at the University of Helsinki, Finland, started working on some simple ideas for an operating system. He started with a task switcher in Intel 80386 assembly language and a terminal driver. On 25 August 1991, Torvalds posted the following to comp.os.minix, a newsgroup on Usenet:
On 17 September 1991, Torvalds prepared version 0.01 of Linux and put on the "" – FTP server of the Finnish University and Research Network. It was not even executable since its code still needed Minix for compilation and play.
On 5 October 1991, Linus announced the first "official" version of Linux, version 0.02. At this point, Linux was able to run Bash, GCC, and some other GNU utilities:
After that, many people contributed code to the project, included some developers from the MINIX community. At the time, the GNU Project had created many of the components required for a free operating system, but its own kernel, GNU Hurd, was incomplete and unavailable. The Berkeley Software Distribution had not yet freed itself from legal encumbrances. Despite the limited functionality of the early versions, Linux rapidly gained developers and users.
Torvalds assigned version 0 to the kernel to indicate that it was mainly for testing and not intended for productive use. Version 0.11, released in December 1991, was the first self-hosted Linux, for it could be compiled by a computer running the same kernel.
When Torvalds released version 0.12 in February 1992, he adopted the GNU General Public License version 2 over his previous self-drafted license, which had not permitted commercial redistribution. In contrast to Unix, all source files of Linux are freely available, including device drivers. The initial success of Linux was driven by programmers and testers across the world. With the support of the POSIX APIs, through the libC that, whether needed, acts as an entry point to the kernel address space, Linux could run software and applications that had been developed for Unix.
On 19 January 1992, the first post to the new newsgroup alt.os.linux was submitted. On 31 March 1992, the newsgroup was renamed comp.os.linux. The fact that Linux is a monolithic kernel rather than a microkernel was the topic of a debate between Andrew S. Tanenbaum, the creator of MINIX, and Torvalds. The Tanenbaum–Torvalds debate started in 1992 on the Usenet group comp.os.minix as a general discussion about kernel architectures.
Linux version 0.95 was the first to be capable of running the X Window System. In March 1994, Linux 1.0.0 was released with 176,250 lines of code. It was the first version suitable for use in production environments.
It started a versioning system for the kernel with three or four numbers separated by dots where the first represented the major release, the second was the minor release, and the third was the revision. At that time odd-numbered minor releases were for development and tests, whilst even numbered minor releases were for production. The optional fourth digit indicated a set of patches to a revision. Development releases were indicated with -rc suffix.
The current version numbering is slightly different from the above. The even vs. odd numbering has been dropped and a specific major version is now indicated by the first two numbers, taken as a whole. While the time-frame is open for the development of the next major, the -rcN suffix is used to identify the n'th release candidate for the next version. For example, the release of the version 4.16 was preceded by seven 4.16-rcN. Once a stable release is made, its maintenance is passed off to the “stable team". Occasional updates to stable releases are identified by a three numbering scheme.
After version 1.3 of the kernel, Torvalds decided that Linux had evolved enough to warrant a new major number, so he released version 2.0.0 in June 1996.
Starting with version 2.0, Linux is configurable for selecting specific hardware targets and for enabling architecture specific features and optimizations. The make *config family of commands of kbuild are used to enable and configure thousands of options for building ad hoc kernel executables and loadable modules.
The kernel supports several file system, some that have been designed for Linux, like ext3, ext4, Btrfs, and others that are native of other operating systems like Minix, Xenix, Irix, Solaris, System V, Windows and MS-DOS.
In 2005 the stable team was formed as a response to the lack of a kernel tree where people could work on bug fixes, and it would keep updating stable versions. In February 2008 the linux-next tree to serve as a place where patches aimed to be merged during the next development cycle gathered. Several subsystem maintainers also adopted the suffix -next for trees containing code which they mean to submit for inclusion in the next release cycle., the in-development version of Linux is held in an unstable branch named linux-next.
Linux used to be maintained without the help of an automated source code management system until, in 2002, development switched to BitKeeper. It was freely available for Linux developers but it was not free software. In 2005, because of efforts to reverse-engineer it, the company which owned the software revoked the support of the Linux community. In response, Torvalds and others wrote Git. The new system was written within weeks, and in two months the first official kernel made using it was released.
The 20th anniversary of Linux was celebrated by Torvalds in July 2011 with the release of the 3.0.0 kernel version. As 2.6 has been the version number for 8 years, a new uname26 personality that reports 3.x as 2.6.40+x had to be added to the kernel so that old programs would work.
Stable 3.x.y kernels were released until 3.19 in February 2015, with development releases carrying the -rc designation. To account for the occasional special patch release, the version 3 series of the kernel added a fourth digit to the version numbering. In April 2015, Torvalds released kernel version 4.0. By February 2015, Linux had received contributions from nearly 12,000 programmers from more than 1,200 companies, including some of the world's largest software and hardware vendors. Version 4.1 of Linux, released in June 2015, contains over 19.5 million lines of code contributed by almost 14,000 programmers.


According to the Stack Overflow’s annual Developer Survey of 2019, more than the 53% of all respondents have developed software for Linux OS and about 27% for Android, although only about 25% develop with Linux-based operating systems.
Most of the website servers use Linux OS and all of the world's 500 most powerful supercomputers use some kind of OS based on Linux.
Linux distributions bundle the kernel with system software and a wide selection of application software, but their usage share in desktops is low in comparison to other operating systems.
The Android OS, which counts the majority of the installed base of all operating systems for mobile devices, is responsible for the rising usage of the Linux kernel, together with its wide use in a large variety of embedded devices.


Linux is a monolithic kernel with a modular design, supporting most features once only available in closed source kernels of non-free operating systems:
Device drivers and kernel extensions run in kernel space, with full access to the hardware, although some exceptions run in user space, for example, filesystems based on FUSE/CUSE, and parts of UIO. The graphics system most people use with Linux does not run within the kernel. Unlike standard monolithic kernels, device drivers are easily configured as modules, and loaded or unloaded while the system is running and can also be pre-empted under certain conditions in order to handle hardware interrupts correctly and to better support symmetric multiprocessing. By choice, Linux has no stable device driver application binary interface.
Linux typically makes use of memory protection and virtual memory and can also handle non-uniform memory access, however the project has absorbed μClinux which also makes it possible to run Linux on microcontrollers without virtual memory.
The hardware is represented in the file hierarchy. User applications interact with device drivers via entries in the or directories. Processes information as well are mapped to the file system through the directory.

Programming language and coding style

Linux is written in a special C programming language supported by GCC, a compiler that extends in many ways the C standard, for example using inline sections of code written in the assembly language of the target architecture. Since 2002 all the code must adhere to the 21 rules comprising the Linux Kernel Coding Style.

GNU toolchain

The GNU Compiler Collection is the default compiler for the mainline Linux sources and it's invoked by a utility called make. Then, the GNU Assembler outputs the object files from the GCC generated assembly code. Finally, the GNU Linker is used to produce a statically linked executable kernel file called vmlinux. as and ld are part of a package called GNU binutils. The above-mentioned tools are collectively known as the GNU toolchain.

Compiler compatibility

GCC was for a long time the only compiler capable of correctly building Linux. In 2004, Intel claimed to have modified the kernel so that its C compiler was also capable of compiling it. There was another such reported success in 2009, with a modified 2.6.22 version.
Since 2010, effort has been underway to build Linux with Clang, an alternative compiler for the C language; as of 12 April 2014, the official kernel could almost be compiled by Clang. The project dedicated to this effort is named LLVMLinux after the LLVM compiler infrastructure upon which Clang is built. LLVMLinux does not aim to fork either Linux or the LLVM, therefore it is a meta-project composed of patches that are eventually submitted to the upstream projects. By enabling Linux to be compiled by Clang, developers may benefit from shorter compilation times.


Linux is a clone of UNIX, therefore it aims towards POSIX and Single UNIX Specification compliance.
Furthermore, since Linux is not UNIX, the kernel provides additional system calls and other interfaces that are Linux specific. In order to be included in the official kernel, the code must comply with a set of well defined licensing rules.

Kernel-to-userspace API

The set of the Linux kernel API that regard the interfaces exposed to user applications is fundamentally composed by UNIX and Linux-specific system calls. A system call is an entry point into the Linux kernel. For example, among the Linux-specific ones there is the family of the clone system calls. Most extensions must be enabled by defining the _GNU_SOURCE macro in a header file or when the user-land code is being compiled.
System calls can only be invoked by using assembly instructions which enable the transition from unprivileged user space to privileged kernel space in ring 0. For this reason, the C standard library acts as a wrapper to most Linux system calls, by exposing C functions that, only whether it is needed, can transparently enter into the kernel which will execute on behalf of the calling process. For those system calls not exposed by libC, e.g. the fast userspace mutex, the library provides a function called syscall which can be used to explicitly invoke them.
Pseudo filesystems and special files constitute another layer of interface to kernel data structures representing hardware or logical devices.

Kernel-to-userspace ABI

Because of the differences existing between the hundreds of various implementations of the Linux OS, executable objects, even though they are compiled, assembled, and linked for running on a specific hardware architecture, often cannot run on different Linux Distributions. This issue is mainly due to distribution-specific configurations and set of patches applied to the code of the Linux kernel, differences in system libraries, services, filesystem hierarchies, and environment variables.
The main standard concerning application and binary compatibility of Linux distributions is the Linux Standard Base. However, the LSB goes beyond what concerns the Linux kernel, because it also defines the desktop specifications, the X libraries and Qt that have little to do with it. The LSB version 5 is built upon several standards and drafts.
The parts of the LSB largely relevant to the kernel are the General ABI, especially the System V ABI and the Executable and Linkable Format, and the Processor Specific ABI, for example the Core Specification for X86-64.
The standard ABI for how x86_64 user programs invoke system calls is to load the syscall number into the rax register, and the other parameters into rdi, rsi, rdx, r10, r8, and r9, and finally to put the syscall assembly instruction in the code.

In-kernel API

There are several kernel internal APIs utilized between the different subsystems. Some are available only within the kernel subsystems, while a somewhat limited set of in-kernel symbols is exposed also to dynamically loadable modules whether they're exported with the EXPORT_SYMBOL and EXPORT_SYMBOL_GPL macros.
Some Linux in-kernel APIs have been kept stable over several releases, others have not. There are no guarantees regarding the in-kernel APIs. Maintainers and contributors are free to augment or change them at any time. However, there are in-kernel APIs that manipulate data structures or perform common routines that have remained stable at least since Linux version 2.6.
Examples of in-kernel APIs include libraries of low-level common services used by device drivers:
The Linux developers choose not to maintain a stable in-kernel ABI. Modules compiled for a specific Linux cannot be loaded into another version of the kernel without being re-compiled, assuming that the source level in-kernel API has remained the same, otherwise also the module code must be modified accordingly.

Technical features

Processes and Threads

Linux creates processes by means of the clone or by the newer clone3 system calls. Depending on the given parameters, the new entity can share most or none of the resources of the caller. These syscalls can create new entities ranging from new independent processes, to new threads of execution within the calling process. In this latter case the new entity owns the same TGID of the calling process and consequently has also the same PID in userspace.
The Native POSIX Thread Library, simply known as the NPTL, provides the standard POSIX threads interface to userspace Whenever a new thread is created using the pthread_create POSIX interface, the clone family of system calls must also be given the address of the function that the new thread must jump to. The Linux kernel provides the futex mechanisms for fast user-space locking and synchronization; the majority of the operations are performed in userspace but it may be necessary to communicate with the kernel using the futex system call.
Differently, whenever an independent process is created, the syscalls return exactly to the next instruction of the same program, concurrently in parent process and in child's one. Different return values enable the program to know in which of the two processes it is currently executing. Programs need this information because the child process, a few steps after process duplication, usually invokes the execve system call and replace the program that is currently being run by the calling process with a new program, with newly initialized stack, heap, and  data segments. When it's done, it results in two processes that run two different programs.

Scheduling and Preemption

The Linux scheduler enables different classes and policies. By default the kernel uses a scheduler mechanism called the Completely Fair Scheduler introduced in the 2.6.23 version of the kernel. Internally this default-scheduler class is also known as SCHED_OTHER, but the kernel also contains two POSIX-compliant real-time scheduling classes named SCHED_FIFO and SCHED_RR, both of which take precedence over the default class. An additional scheduling policy known as SCHED_DEADLINE, implementing the earliest deadline first algorithm, was added in kernel version 3.14, released on 30 March 2014. SCHED_DEADLINE takes precedence over all the other scheduling classes.
Linux provides both user preemption as well as full kernel preemption. Preemption reduces latency, increases responsiveness, and makes Linux more suitable for desktop and real-time applications.
With user preemption, the kernel scheduler can replace the current process with the execution of a context switch to a different one that therefore acquires the computing resources for running. It makes it according to the CFS algorithm, to the active scheduler policy and to the processes relative priorities. With kernel preemption, the kernel can preempt itself when an interrupt handler returns, when kernel tasks block, and whenever a subsystem explicitly calls the schedule function.
Through the use of the real-time Linux kernel patch PREEMPT_RT, support for full preemption of critical sections, interrupt handlers, and "interrupt disable" code sequences can be supported. Partial mainline integration of the real-time Linux patches already brought some functionality to the kernel mainline.

Memory and Address Spaces

Inter Process Communication and Synchronization

Input/Output Layer

Virtual and Concrete Filesystems

Device Drivers


While not originally designed to be portable, Linux is now one of the most widely ported operating system kernels, running on a diverse range of systems from the ARM architecture to IBM z/Architecture mainframe computers. The first port was performed on the Motorola 68000 platform. The modifications to the kernel were so fundamental that Torvalds viewed the Motorola version as a fork and a "Linux-like operating system". However, that moved Torvalds to lead a major restructure of the code to facilitate porting to more computing architectures. The first Linux that, in a single source tree, had code for more than i386 alone, supported the DEC Alpha AXP 64-bit platform.
Linux runs as the main operating system on IBM's Summit; as of 2019, all of the world's 500 fastest supercomputers run some operating system based on the Linux kernel, a big change from 1998 when the first Linux supercomputer got added to the list.
Linux has also been ported to various handheld devices such as Apple's iPhone 3G and iPod.
Linux forks
There are certain communities that develop kernels based on the official Linux. Some interesting bits of code from these forks that include Linux-libre, Compute Node Linux, Cooperative Linux, Longene, grsecurity, INK, L4Linux, MkLinux, RTLinux, and User-Mode Linux have been merged into the mainline. Some operating systems developed for mobile phones initially used heavily modified versions of Linux, including Google Android, Firefox OS, HP webOS, Nokia Maemo and Jolla Sailfish OS. In 2010, the Linux community criticised Google for effectively starting its own kernel tree:
Today Android uses a slightly customized Linux where changes are implemented in device drivers so that little or no change to the core kernel code is required. Android developers also submit patches to the official Linux that finally can boot the Android operating system. For example, a Nexus 7 can boot and run the mainline Linux.

Kernel panic and oopses

In Linux, a "panic" is an unrecoverable system error detected by the kernel which signals such a condition by calling the panic function located in the header file. Most panics are the result of unhandled processor exceptions, such as references to invalid memory addresses. They are typically indicative of a bug in kernel code. Others can also indicate a failure of hardware, caused by a processor bug, overheating/damaged CPU, RAM, and motherboard soft errors.
A report of a non-fatal bug in the kernel is called an "oops"; such deviations from correct behavior of the Linux kernel may allow continued operation with compromised reliability.

Live patching

Rebootless updates can even be applied to the kernel by using live patching technologies such as Ksplice, kpatch and kGraft. Minimalistic foundations for live kernel patching were merged into the Linux kernel mainline in kernel version 4.0, which was released on 12 April 2015. Those foundations, known as livepatch and based primarily on the kernel's ftrace functionality, form a common core capable of supporting hot patching by both kGraft and kpatch, by providing an application programming interface for kernel modules that contain hot patches and an application binary interface for the userspace management utilities. However, the common core included into Linux kernel 4.0 supports only the x86 architecture and does not provide any mechanisms for ensuring function-level consistency while the hot patches are applied., there is ongoing work on porting kpatch and kGraft to the common live patching core provided by the Linux kernel mainline.


is a much-publicized topic in relation to the Linux kernel because a large portion of the kernel bugs present potential security flaws. For example, they may allow for privilege escalation or create denial-of-service attack vectors. Over the years, numerous such flaws were found and fixed in the Linux kernel. New security features are frequently implemented to improve the Linux kernel's security.
Linux offers a wealth of mechanisms to reduce kernel attack surface and improve security which are collectively known as the Linux Security Modules. They comprise the Security-Enhanced Linux ''' module, whose code has been originally developed and then released to the public by the NSA, and AppArmor among others. SELinux is now actively developed and maintained on GitHub. SELinux and AppArmor provide support to access control security policies, including mandatory access control, though they profoundly differ in complexity and scope.
Another security feature is the Seccomp BPF which works by filtering parameters and reducing the set of system calls available to user-land applications.
Critics have accused kernel developers of covering up security flaws or at least not announcing them; in 2008, Linus Torvalds responded to this with the following:
Linux distributions typically release security updates to fix vulnerabilities in the Linux kernel. Many offer long-term support releases that receive security updates for a certain Linux kernel version for an extended period of time.

Feature history

Version 1.0 of the Linux kernel was released on 14 March 1994. This release of the Linux kernel only supported single-processor i386-based computer systems. Portability became a concern, and so version 1.2 gained support for computer systems using processors based on the Alpha, SPARC, and MIPS architectures.
Version 2.0 was released on 9 June 1996. The series included 41 releases. The major feature of 2.0 was support for symmetric multiprocessing and support for more types of processors.
Version 2.2, released on 20 January 1999, removed the global spinlock and provided improved SMP support, added support for the m68k and PowerPC architectures, and added new file systems. In 1999, IBM published its patches to the Linux 2.2.13 code for the support of the S/390 architecture.
Version 2.4.0, released on 4 January 2001, contained support for ISA Plug and Play, USB, and PC Cards. It also included support for the PA-RISC processor from Hewlett-Packard. Development for 2.4.x changed a bit in that more features were made available throughout the duration of the series, including support for Bluetooth, Logical Volume Manager version 1, RAID support, InterMezzo and ext3 file systems.
Version 2.6.0 was released on 17 December 2003. The development for 2.6.x changed further towards including new features throughout the duration of the series. Among the changes that have been made in the 2.6 series are: integration of µClinux into the mainline kernel sources, PAE support, support for several new lines of CPUs, integration of Advanced Linux Sound Architecture into the mainline kernel sources, support for up to 232 users, support for up to 229 process IDs, substantially increased the number of device types and the number of devices of each type, improved 64-bit support, support for file systems which support file sizes of up to 16 terabytes, in-kernel preemption, support for the Native POSIX Thread Library, User-mode Linux integration into the mainline kernel sources, SELinux integration into the mainline kernel sources, InfiniBand support, and considerably more. Also notable are the addition of several file systems throughout the 2.6.x releases: FUSE, JFS, XFS, ext4 and more. Details on the history of the 2.6 kernel series can be found in the ChangeLog files on the 2.6 kernel series source code release area of
Version 3.0 was released on 22 July 2011. On 30 May 2011, Torvalds announced that the big change was "NOTHING. Absolutely nothing." and asked, "...let's make sure we really make the next release not just an all new shiny number, but a good kernel too." After the expected 6–7 weeks of the development process, it would be released near the 20th anniversary of Linux.
On 11 December 2012, Torvalds decided to reduce kernel complexity by removing support for i386 processors, making the 3.7 kernel series the last one still supporting the original processor. The same series unified support for the ARM processor.
Version 3.11, released on 2 September 2013, adds many new features such as new O_TMPFILE flag for to reduce temporary file vulnerabilities, experimental AMD Radeon dynamic power management, low-latency network polling, and zswap.
Version 5.0, released in 2019, includes patches for the Spectre and Meltdown security vulnerabilities and other feature enhancements.
The numbering change from 2.6.39 to 3.0, and from 3.19 to 4.0, involved no meaningful technical differentiation. The major version number was increased to avoid large minor numbers.


Developer community

It is generally assumed that the community of Linux kernel developers comprises 5000 or 6000 members. According to the "2017 State of Linux Kernel Development", a study issued by the Linux Foundation, covering the commits for the releases 4.8 to 4.13, about 1500 developers were contributing from about 200-250 companies on average. The top 30 developers contributed a little more than 16% of the code. As of companies, the top contributors are Intel and Red Hat, Linaro, IBM, the second and fifth places are held by the 'none' and 'unknown' categories.

Submitting code to the kernel

A developer who wants to change the Linux kernel starts with developing and testing that change. Depending on how significant the change is and how many subsystems it modifies, the change will either be submitted as a single patch or in multiple patches of source code. In case of a single subsystem that is maintained by a single maintainer, these patches are sent as e-mails to the maintainer of the subsystem with the appropriate mailing list in Cc. The maintainer and the readers of the mailing list will review the patches and provide feedback. Once the review process has finished the subsystem maintainer accepts the patches in the relevant Git kernel tree. If the changes to the Linux kernel are bug fixes that are considered important enough, a pull request for the patches will be sent to Torvalds within a few days. Otherwise, a pull request will be sent to Torvalds during the next merge window. The merge window usually lasts two weeks and starts immediately after the release of the previous kernel version. The Git kernel source tree names all developers who have contributed to the Linux kernel in the Credits directory and all subsystem maintainers are listed in Maintainers.

Development model

The Linux kernel project integrates new code on a rolling basis. Software checked into the project must work and compile without error. For each kernel subsystem there is a maintainer who is responsible for reviewing patches against the kernel code standards and keeps a queue of patches that can be submitted to Linus Torvalds within a merge window of several weeks. Patches are merged by Torvalds into the source code of the prior stable Linux kernel release, creating the -rc release candidate for the next stable kernel. Once the merge window is closed only fixes to the new code in the development release are accepted. The -rc development release of the kernel goes through regression tests and once it is judged to be stable by Torvalds and the kernel subsystem maintainers a new Linux kernel is released and the development process starts all over again.
Developers who feel treated unfairly can report this to the Linux Foundation's Technical Advisory Board. In July 2013 the maintainer of the USB 3.0 driver Sarah Sharp asked Torvalds to address the abusive commentary in the kernel development community. In 2014, Sharp backed out of Linux kernel development, saying that "The focus on technical excellence, in combination with overloaded maintainers, and people with different cultural and social norms, means that Linux kernel maintainers are often blunt, rude, or brutal to get their job done". At the conference in 2018, developers expressed the view that the culture of the community has gotten much better in the past few years. Daniel Vetter, the maintainer of the Intel drm/i915 graphics kernel driver, commented that the "rather violent language and discussion" in the kernel community has decreased or disappeared.
Laurent Pinchart asked developers for feedback on their experience with the kernel community at the 2017 Embedded Linux Conference Europe. The issues brought up were a few days later discussed at the Maintainers Summit. Concerns over the lack of consistency in how maintainers responded to patches submitted by developers were echoed by Shuah Khan, the maintainer of the kernel self-test framework. Torvalds contended that there would never be consistency in the handling of patches because different kernel subsystems have over time adopted different development processes. Therefore, it was agreed upon that each kernel subsystem maintainer would document the rules for patch acceptance.

Development community conflicts

There have been several notable conflicts among Linux kernel developers. Examples of such conflicts are:
Prominent Linux kernel developers have been aware of the importance of avoiding conflicts between developers. For a long time there has been no code of conduct for kernel developers due to opposition by Linus Torvalds. However, a Linux Kernel Code of Conflict was introduced on 8 March 2015. It was replaced on 16 September 2018 by a new Code of Conduct based on the Contributor Covenant. This coincided with a public apology by Linus and a brief break from kernel development. On 30 November 2018, complying with the Code of Conduct, Jarkko Sakkinen of Intel sent out patches replacing instances of "fuck" appearing in source code comments with suitable versions focused on the word 'hug'.


, the 5.6 release of the Linux kernel had around 33 million lines of code, roughly 14% of the code is part of the "core" while 60% is drivers.

Estimated cost to redevelop

The cost to redevelop the Linux kernel version 2.6.0 in a traditional proprietary development setting has been estimated to be US$612 million in 2004 prices using the COCOMO man-month estimation model. In 2006, a study funded by the European Union put the redevelopment cost of kernel version 2.6.8 higher, at €882M.
This topic was revisited in October 2008 by Amanda McPherson, Brian Proffitt, and Ron Hale-Evans. Using David A. Wheeler's methodology, they estimated redevelopment of the 2.6.25 kernel now costs $1.3bn. Again, Garcia-Garcia and Alonso de Magdaleno from University of Oviedo estimate that the value annually added to kernel was about €100M between 2005 and 2007 and €225M in 2008, it would cost also more than €1bn to develop in the European Union.
, using then-current LOC of a 2.6.x Linux kernel and wage numbers with David A. Wheeler's calculations it would cost approximately $3bn to redevelop the Linux kernel as it keeps getting bigger. An updated calculation as of 2018, using then-current 20,088,609 LOC for the 4.14.14 Linux kernel and the current US National average programmer salary of $75,506 show it would cost approximately $14,725,449,000 dollars to rewrite the existing code.

Maintenance and long-term support

The latest kernel version and older kernel versions are maintained separately. Most latest kernel releases were supervised by Linus Torvalds. Current versions are released by Greg Kroah-Hartman.
The Linux kernel developer community maintains a stable kernel by applying fixes for software bugs that have been discovered during the development of the subsequent stable kernel. Therefore, will always list two stable kernels. The next stable Linux kernel is now released only 8 to 12 weeks later. Therefore, the Linux kernel maintainers have designated some stable kernel releases as longterm, these long-term support Linux kernels are updated with bug fixes for two or more years. In November 2019 there were five longterm Linux kernels: 4.19.84, 4.14.154, 4.9.201, 4.4.201 and 3.16.76. The full list of releases is at Linux kernel version history.

Relation with Linux distributions

Most Linux users run a kernel supplied by their Linux distribution. Some distributions ship the "vanilla" or "stable" kernels. However, several Linux distribution vendors maintain another set of Linux kernel branches which are integrated into their products. These are usually updated at a slower pace compared to the "vanilla" branch, and they usually include all fixes from the relevant "stable" branch, but at the same time they can also add support for drivers or features which had not been released in the "vanilla" version the distribution vendor started basing their branch from.

Legal aspects

GNU GPLv2 licensing terms

The Linux kernel is released under the GNU General Public License version 2 only, with some firmware images released under various non-free licenses.
Initially, Torvalds released Linux under a license which forbade any commercial use, thus making it proprietary. This was changed in version 0.12 by a switch to the GNU General Public License version 2. This license allows distribution and sale of possibly modified and unmodified versions of Linux but requires that all those copies be released under the same license and be accompanied by the complete corresponding source code. Torvalds has described licensing Linux under the GPLv2 as the "best thing I ever did".
The Linux kernel is licensed explicitly only under version 2 of the GPL, without offering the licensee the option to choose "any later version", which is a common GPL extension. There was considerable debate about how easily the license could be changed to use later GPL versions, and whether this change is even desirable. Torvalds himself specifically indicated upon the release of version 2.4.0 that his own code is released only under version 2. However, the terms of the GPL state that if no version is specified, then any version may be used, and Alan Cox pointed out that very few other Linux contributors had specified a particular version of the GPL.
In September 2006, a survey of 29 key kernel programmers indicated that 28 preferred GPLv2 to the then-current GPLv3 draft. Torvalds commented, "I think a number of outsiders... believed that I personally was just the odd man out because I've been so publicly not a huge fan of the GPLv3." This group of high-profile kernel developers, including Torvalds, Greg Kroah-Hartman and Andrew Morton, commented on mass media about their objections to the GPLv3. They referred to clauses regarding DRM/tivoization, patents, "additional restrictions" and warned a Balkanisation of the "Open Source Universe" by the GPLv3. Linus Torvalds, who decided not to adopt the GPLv3 for the Linux kernel, reiterated his criticism even years later.

Loadable kernel modules

It is debated whether loadable kernel modules are to be considered derivative works under copyright law, and thereby fall under the terms of the GPL.
Torvalds has stated his belief that LKMs using only a limited, "public" subset of the kernel interfaces can sometimes be non-derived works, thus allowing some binary-only drivers and other LKMs that are not licensed under the GPL. A good example for this is the usage of dma_buf by the proprietary Nvidia graphics drivers. dma_buf is a recent kernel feature, which allows multiple GPUs to quickly copy data into each other's framebuffers. One possible use case would be Nvidia Optimus that pairs a fast GPU with an Intel integrated GPU, where the Nvidia GPU writes into the Intel framebuffer when it is active. But, Nvidia cannot use this infrastructure because it uses a technical means to enforce the rule that it can only be used by LKMs that are also GPL. Alan Cox replied on LKML, rejecting a request from one of their engineers to remove this technical enforcement from the API. Not all Linux kernel contributors agree with this interpretation, however, and even Torvalds agrees that many LKMs are clearly derived works, and indeed he writes that "kernel modules ARE derivative 'by default'".
On the other hand, Torvalds has also said that "one gray area in particular is something like a driver that was originally written for another operating system. THAT is a gray area, and _that_ is the area where I personally believe that some modules may be considered to not be derived works simply because they weren't designed for Linux and don't depend on any special Linux behaviour". Proprietary graphics drivers, in particular, are heavily discussed. Ultimately, it is likely that such questions can only be resolved by a court.

Firmware binary blobs

The official kernel, that is the Linus git branch at the repository, contains proprietary code, despite its license forbidding this. Linux can also search the filesystems to locate proprietary firmware, drivers, and other executable modules, then it can load and link them into the kernel space. Whenever proprietary modules are loaded into Linux, the kernel marks itself as being "tainted" and therefore bug reports from tainted kernels will often be ignored by developers.
Whether it's needed firmware can be built-in to the kernel, this means building the firmware into vmlinux; however this is not always a viable option for technical or legal issues.
In 2002, Richard Stallman stated why, in his point of view, such blobs make the Linux kernel partially non-free software, and that distributing Linux kernel "violates the GPL", which requires "complete corresponding source code" to be available.
In 2008, Free Software Foundation Latin America started Linux-libre as a project that creates a completely free variant of the Linux kernel without proprietary objects; it is used by certain completely free Linux distributions, such as those endorsed by the Free Software Foundation, while it can also be used on most distributions.


Linux is a registered trademark of Linus Torvalds in the United States, the European Union, and some other countries. This is the result of an incident in which William Della Croce, Jr., who was not involved in the Linux project, trademarked the name and subsequently demanded royalties for its use. Several Linux backers retained legal counsel and filed suit against Della Croce. The issue was settled in August 1997 when the trademark was assigned to Linus Torvalds.