Linux 7.3
- ID
- 36951
- Status
- summarized
- Published
- 19 Oct 2026, 3:23 PM
- Fetched
- 20 Oct 2026, 2:43 AM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://lwn.net/Articles/1101143/
- Source URL
- https://hnrss.org/best
Summary
- Score
- 5.5
- Created
- 20 Oct 2026, 2:45 AM
- Tags
- Audience
- developers
What happened
Linus Torvalds released the 7.3 kernel on Sunday 18 October 2026, a release LWN describes as a record-breaker: 18,765 non-merge commits from 3,021 developers, 807 of them first-time kernel contributors. Headline changes include completed sched_ext subscheduler support, global per-CPU data for BPF programs, binfmt_misc extensions, the new fchroot() system call, working-set tracking for VMs, a deliberately failing failfs filesystem, ntfs3 alternative data streams, and a long list of SMB server improvements. The merge window for 7.4 opens the next day, though Torvalds notes his schedule will be irregular due to an annual family vacation.
Why it matters
For most builders this changes nothing this week: there is no security fix or API break named here that forces action, and distro and cloud-image uptake typically trails a .0 release by weeks. The two items worth a look if you run latency-sensitive or instrumented workloads are sched_ext reaching completion and per-CPU global data for BPF programs; everything else (failfs, fchroot(), ntfs3 streams) is niche or test-only. The 807 first-time contributors is the more interesting long-run signal if you depend on out-of-tree modules or maintain a downstream patch set.
Discussion angle
The thread drew 561 points and 253 comments on a routine release note, and the top replies are about learning kernel development rather than the features. Worth asking live: what actually makes a kernel release newsworthy to you — version numbers, or the 807 first-timers and what that says about maintainer pipeline and downstream patch churn?