Linux 7.3-rc7 lands as the final release candidate, selftest-heavy diffstat and all
Linux 7.3-rc7 shipped on October 12 with half the patch made up of selftests and an ext4 data=journal deprecation on board, keeping the stable release on track for October 18.
Linus Torvalds released Linux 7.3-rc7 on October 12, the last planned release candidate on the road to the next stable release of the Linux kernel. Per Phoronix’s report on the announcement, the final 7.3 release is still set for next weekend, October 18, unless something new comes up between now and then. Two things stand out in this particular rc: an unusual diffstat, and a filesystem deprecation arriving at the very tail of the cycle.
The oddity Torvalds himself flagged is the diffstat — the summary table at the foot of a release announcement, tallying which files a patch touches and by how much. This one is slightly strange, by his own description: half the patch consists of selftests. Selftests are the kernel’s in-tree test suite, code that lives in the same source tree as the kernel it exercises and therefore counts in the same statistics as driver fixes and architecture work. A late-stage rc dominated by test code is not the usual shape, which is presumably why Torvalds called it out rather than letting the numbers speak for themselves. His notes also take up AI-assisted patches.
There is a reasonable reading of that shape, and it is a benign one. Test code does not change how the kernel behaves for anyone running it, which makes it just about the safest category of change to accept while a tree is supposed to be settling down ahead of a release. A final rc that is half selftests suggests the functional surface of 7.3 has been stable for some time, and that the work still arriving at the margins is going toward verifying that stability rather than disturbing it. Read that way, the odd diffstat is less a warning than a snapshot of where the cycle’s remaining energy went.
The more consequential item in rc7 is one most people running the kernel will never notice. LWN’s prepatch coverage notes the deprecation of ext4’s data=journal mode, now slated to be removed entirely at the beginning of 2028. It is the most conservative of ext4’s journaling modes — the mode journals the file data itself, not just the metadata that describes it, buying the strongest consistency guarantee ext4’s mount options offer at a real cost in performance. Anyone still depending on it has a published removal date and more than a year of runway to migrate to one of the other modes; until the removal actually lands, nothing stops working. What is unusual is the delivery vehicle. Deprecation notices normally arrive early in a merge window, when the tree has just been opened up — not in the seventh release candidate, when it is supposed to be sealed. In practice, a deprecation is a notice rather than a switch, exactly the kind of change that can ride in a final rc without putting a release date at risk.
The schedule is the quiet part of the story. An rc7 landing on October 12 with the final release expected the following weekend is the kernel’s release discipline working as designed: the date sits on the calendar, and the release happens when the calendar says so, not when a feature list is complete. The only caveat is the one the announcement itself carries — something new could still come up. If nothing does, 7.3 ships next weekend, and most of the people who eventually run it will never have seen the seam.
For a project this size, the most revealing documents are often its most routine ones. A final release candidate whose substance is half tests and a deprecation notice with a removal date more than a year out says more about where kernel development attention is sitting than any list of headline features would. Mostly, though, rc7 says the cycle is ending the way cycles are supposed to: on time, and without drama.