logo
Kurashizu Blogwhere ideas flow
  • Home
  • News
  • Blog
  • About
  • Home
  • News
  • Blog
  • About

© 2026 Kurashizu. All rights reserved.

Admin·New Post·Service Status
Powered by Cloudflare·30.10.26
← Back to news

Linux bugs fixed per release over time: >2× rise since 2026-04

Original article
lwn.net|25 points|4 comments|by farlight|Oct 17, 2026

Analysis of Linux Kernel 7.2 Development Metrics: A Surge in Activity

LWN.net Logo

On August 17, 2026, Linus Torvalds officially launched the 7.2 kernel. Despite the release, Torvalds expressed some reservations regarding the volume of incoming fixes, stating they were:

"bigger than I would have wished for"

The development cycle for 7.2 stands as one of the most intense in the project's history, characterized by the addition of nearly 600,000 lines of code.

📈 High-Level Development Statistics

The scale of this release is staggering. To understand the growth, we can look at the commit volume. There were 16,418 non-merge commits integrated into the mainline.

This was the busiest release ever →\rightarrow→ Actually, it is the second-busiest in history. While the 6.7 release saw more commits, that spike was primarily due to the massive integration of the bcachefs history. In contrast, the activity in 7.2 is far more distributed across various subsystems.

Contribution Growth

The community continues to expand. A total of 2,652 developers contributed to this release, shattering the previous record of 2,479 set by version 7.1.

The general trend since the adoption of Git can be summarized by the following growth ratio: Growth Rate≈DeveloperscurrentDeveloperspast>2×\text{Growth Rate} \approx \frac{\text{Developers}_{current}}{\text{Developers}_{past}} > 2\timesGrowth Rate≈Developerspast​Developerscurrent​​>2×

Developer Plot


🏆 Top Contributors

The effort was split between those providing the most individual changesets and those contributing the largest volumes of code.

Most Active by Changesets

DeveloperChangesets% of Total
Uwe Kleine-König1510.9%
Rosen Penev1460.9%
Ian Rogers1380.8%
Johan Hovold1330.8%
Arnaldo Carvalho de Melo1310.8%

Most Active by Lines Changed

DeveloperLines Added/Modified% of Total
Matthew Stewart83,5878.4%
Hawking Zhang62,8936.3%
Miguel Ojeda38,9793.9%
Ian Rogers31,9493.2%
Darren Ye20,8432.1%

Key Technical Highlights

  • Uwe Kleine-König: Focused heavily on cleaning up the driver subsystem.
  • Rosen Penev: Notable for submitting a large volume of LLM-authored bug fixes across crypto, networking, drivers, and architecture.
  • Ian Rogers & Arnaldo Carvalho de Melo: Concentrated their efforts on the perf tool for user-space.
  • Johan Hovold: Improved the USB and SPI subsystems.
  • Matthew Stewart & Hawking Zhang: Topped the line counts by adding massive, machine-generated amdgpu header files.
  • Miguel Ojeda: Integrated the zerocopy Rust crate into the kernel.

Example of the type of machine-generated headers added:

/* Auto-generated header for amdgpu */
#define AMDGPU_REG_X 0x12345678
#define AMDGPU_REG_Y 0x87654321
// ... thousands of similar lines ...

🔍 Quality Assurance and Review

The community relies on specific tags to ensure stability. In 7.2, the distribution was as follows:

  • Reviewed-by tags: 48%
  • Tested-by tags: ~8%

Review Tags Plot

There is a slight downward trend in the use of review tags. It remains uncertain if this indicates a drop in actual review activity or simply a change in how tags are applied.

Top QA Credits

RoleLead ContributorCount
Tested-byDan Wheeler117
Reviewed-byKonrad Dybcio231
Reviewed-byDmitry Baryshkov225

Note: Dybcio and Baryshkov continue to lead reviews for Qualcomm-related devicetree and driver files.


🏢 Corporate and Independent Support

A total of 249 employers were identified as supporting the 7.2 cycle.

Employer Impact

EmployerBy Changesets (%)By Lines Changed (%)
(Unknown)16.7%10.4%
Intel9.2%5.4%
Google7.3%10.3%
Red Hat5.3%5.2%
AMD5.0%22.4%
Qualcomm4.7%5.9%

First-timers Plot Fixes Plot

The most striking observation in the corporate data is the significant rise in developers with unknown affiliations. This shift suggests a changing landscape in how the kernel is being developed and funded.

LWN Corner