News › linux
By The Linux Camp News, October 20, 2026
The final upstream release changes allocation under VRAM pressure and cgroup CPU scheduling. Filesystem additions expose NTFS streams and let applications reject implicit path lookups, with compatibility limits worth checking.
Linus Torvalds has released Linux 7.3 as a final upstream kernel, not a release candidate, according to LWN's announcement retrieved October 20, 2026. The supplied announcement does not establish an exact release date. Changes include VRAM allocation under contention, cgroup CPU scheduling and filesystem interfaces, including ntfs3 data streams, failfs and fchroot(). 1 4 2
The VRAM change makes memory protection more effective when applications compete for video memory. Kernel Newbies explains that a later-arriving application could previously end up allocating through GTT, system RAM accessible to the GPU, even if it had higher priority. With dmem cgroup protection, allocation instead attempts to evict unprotected buffers before backing off. The benefit is therefore tied to contention and protected allocations, rather than evidence that every GPU workload becomes faster. 2
The reported gaming demonstration needs a separate qualification. It's FOSS says Natalie Vock's full patch set made Indiana Jones and the Great Circle playable with a 9GB demand on an 8GB card, but only the first portion landed in this release. That result cannot establish the performance of Linux 7.3's subset; the supplied evidence lacks a measurement isolating it. 4 3
CPU scheduling changes affect how process groups share CPU time. Kernel Newbies reports four cgroup weight-distribution modes, up, max, concur and tasks, alongside a move to a single runqueue. It describes the default concur mode as the most precise but also the most expensive. The operational inference is to compare latency and scheduling overhead under representative competing workloads: greater allocation precision is not a promise of lower cost everywhere. 2
For ntfs3, alternate data streams expose named data stored alongside a file's ordinary contents. The implementation commit says the driver previously ignored named data attributes. Colon-delimited names now reach them through Linux's ordinary filesystem interfaces, giving applications access without a separate stream-specific interface. 6
The ntfs3 commit documents stream support as enabled by default and ads=0 as the mount option restoring previous behavior. It also leaves stream renaming or moving, and simultaneous creation of a base file and stream, unimplemented. Check those operations before depending on stream-aware workflows. These are the supplied commit's defaults and limits, not independently verified final-tree semantics or claims about every Linux NTFS driver. 6
Failfs changes application assumptions more radically. The supplied development documentation says placing the working directory there rejects working-directory-relative lookups; placing the root there rejects absolute paths, while lookups anchored at explicit directory file descriptors remain usable. This also prevents resolving dynamically linked binaries' interpreters. Applications adopting this model need to audit implicit path use and execution paths, and verify these development-documentation semantics against the final 7.3 tree. 5