Linux 7.3 went stable on Sunday — 18,765 commits from 3,021 developers. Skip the changelog rehash: here's what actually changes for people who run machines, and the checklist to follow before your distro ships it.

Why 7.3 matters more than most point releases

Most kernel releases are a blur of driver updates. 7.3 has several genuinely operator-shaped features:

sched_ext is finally complete. A cgroup can now have its processes managed by its own BPF-based sub-scheduler — different scheduling policies for different workloads on the same box. The scx scheduler family (built for latency-sensitive jobs like game servers and real-time audio) just went from cool experiment to supported interface. If you've been curious about custom schedulers, this is the kernel they were waiting for.

Databases get RWF_DONTCACHE. A database sitting on a raw block device can now tell the kernel per-request: cache this, don't cache that — without the all-or-nothing pain of direct I/O. If you run Postgres or MySQL at scale, this is the kind of quiet primitive that shows up in someone else's benchmark six months from now.

btrfs and ext4 got faster where it hurts. btrfs recovered lost direct-I/O performance and made fsync-heavy logging workloads up to 5x faster; ext4 improved parallel direct-I/O writes and fixed a buffered-write regression. For self-hosters: your Nextcloud or Immich box just got snappier.

Low-end GPUs get fairer VRAM. Improved VRAM contention handling through the dmem cgroup means the application with priority actually gets memory on constrained GPUs. Good news for old AMD APUs, integrated graphics, and gaming handhelds.

XFS learned to check itself. One batch brought lock annotations, health monitoring, scrub-and-repair updates, and media verification. If you run XFS on a NAS or at scale, xfs_scrub now has real teeth — it catches data-integrity problems before they spread.

Sandboxing got a new primitive. failfs — a filesystem where every operation fails — plus the new fchroot(2) syscall let a process drop its filesystem state entirely. Container and sandbox tooling will be building on this for years.

Your Linux NAS can now back up Macs. The in-kernel SMB server gained Apple Time Machine support, per-share SMB3 encryption, and SMB Direct RDMA encryption. Homelab file servers just got more interesting.

When will you actually get it?

  • Arch, CachyOS, and friends: days. Watch your next pacman -Syu.
  • Fedora 45: GA is set for October 30 and RC-1.1 is already in testing — expect 7.3 or something very close.
  • Ubuntu 26.10 "Stonking Stingray": shipped October 15 on the 7.2 series. 7.3 arrives via HWE or mainline builds, not on day one.
  • Debian stable and the LTS crowd: months. Don't hold your breath — that's the deal you signed up for.

The upgrade playbook

  1. Snapshot first. btrfs/snapper or Timeshift — a kernel upgrade you can't roll back is a gamble, not maintenance.
  2. Check out-of-tree modules. NVIDIA driver, ZFS, VirtualBox: wait until each declares 7.3 support. This is where upgrades go to die.
  3. Re-sign if you Secure Boot. Self-signed kernel folks (sbctl users, you know who you are) — re-sign after the upgrade.
  4. Watch your DKMS builds. Don't just assume they compiled; read the log once.
  5. sched_ext curious? Install an scx scheduler and try it on a non-critical box. This is the fun part.
  6. No same-day panic on servers. Nothing here demands an emergency reboot. Schedule it in your maintenance window like a professional.

Sources

  • kernel.org — The Linux Kernel Archives
  • Linus Torvalds' Linux 7.3 release announcement (lore.kernel.org)
  • KernelNewbies — Linux 7.3 changelog
  • LWN — 7.3 merge-window summaries (part 1, part 2)
  • Phoronix — Linux 7.3 release coverage