Linux 7.3 Released: Record Commit Volume Introduces `fchroot()`, Per-CPU BPF Data, and `failfs`
Linus Torvalds has released Linux 7.3, establishing new development volume records with 18,765 non-merge commits from 3,021 contributors. The release introduces structural updates including global per-CPU data for BPF, the `fchroot()` system call, the `failfs` filesystem, and the finalized `sched_ext` subscheduler.
Release Metrics and Execution Window
Linus Torvalds tagged the official release of Linux 7.3 on October 18, 2026. The 7.3 development cycle represents a record-breaking metric across multiple metrics, incorporating 18,765 non-merge commits from 3,021 distinct developers, including 807 first-time contributors. The Linux 7.4 merge window opened immediately following the release, with maintainer integration processing running on a slightly modified schedule due to Torvalds' annual vacation.
Subsystem Updates and Core Architecture
Linux 7.3 introduces targeted feature enhancements across system calls, execution scheduling, memory management, and storage backends:
- BPF Subsystem: Support for global per-CPU data structures inside BPF programs.
- System Calls and Execution: Introduction of the `fchroot()` system call, alongside feature extensions to `binfmt_misc`.
- Filesystems and Storage: Addition of `failfs`, a specialized filesystem designed to fail all operations. The `ntfs3` filesystem driver gained support for alternative data streams, accompanied by an extensive list of updates to the in-kernel SMB server.
- Scheduler Infrastructure: Formal completion of the `sched_ext` subscheduler feature, alongside group-scheduling optimizations targeted at improving execution performance on large systems.
- Virtualization: Native support for virtual machine working-set tracking.
Developer Onboarding and Documentation Ecosystem
The release metrics coincide with discussions regarding technical documentation for incoming kernel developers. While reference materials like The Linux Programming Interface serve userspace API consumers, contributors noted that third-party platforms like KernelNewbies are no longer reliable primary references. The kernel's internal development-process documentation remains the primary, actively maintained path for developers navigating upstream integration.