Linux 7.3-rc3 Released: "Another Fairly Large RC"

# What happened Linux 7.3-rc3 was released as the third weekly test candidate for the 7.3 kernel cycle. Linus Torvalds described it as "Another fairly large rc release," noting an unusual concentration of filesystem fixes alongside the usual stream of driver updates and miscellaneous core fixes. The kernel is progressing toward a planned stable release in the second half of October.

# Scope and notable areas of change The release is broader than a typical rc3 in terms of filesystem changes. Torvalds called out xfs and the smb client specifically, while also pointing to fixes in netfs, afs, erofs, and btrfs. Despite that filesystem footprint, the majority of the patch volume remains driver-related—primarily sound and networking drivers—with GPU driver changes present but smaller.

# What drove many of the fixes This cycle has continued to see a steady inflow of fixes identified via AI/LLM-generated reports and patches. The article notes that many fixes this week were "brewed via AI/LLMs," a trend that has been visible through prior rc releases in this 7.3 development window.

# Other technical hotspots Beyond filesystems and drivers, rc3 includes:

• Core kernel and networking fixes scattered across various subsystems.
• Landlock fixes and updated selftests.
• Architecture-specific fixes, with s390 and powerpc highlighted for this rc.

# Why it matters for users and testers If you run development or test kernels, rc3 is significant for two reasons: the filesystem fixes may affect real-world file operations (EROFS and LZ4 being the clear example), and the driver work means hardware support and stability could shift. Testers should focus on filesystem behaviors and any hardware impacted by sound, networking, or GPU drivers.

# Where this sits in the release timeline Linux 7.3 completed its merge window prior to these weekly release candidates. The rc series is following the normal weekly cadence and is working toward a stable 7.3 release scheduled for the second half of October.

# Quick practical checklist for interested readers

• If you use EROFS with LZ4 rolling decompression, avoid relying on it in production until the corruption issue is resolved.
• Testers should prioritize filesystem tests (xfs, smb, erofs, btrfs) and common networking/sound hardware workflows.
• Keep an eye on subsequent rc releases (rc4, rc5) for follow-up fixes, especially where filesystem fixes are concerned.

# Bottom line