Fedora is launching a week-long community test for Linux kernel 7.2, inviting Fedora 43 and 44 users to vet the new release before it hits stable repositories. The upstream kernel, which landed on August 16, introduces several high-demand updates including enabled Btrfs large folios, partial Apple M3 support, and AMDGPU HDMI 2.1 FRL capabilities. While developers track a specific graphics regression during LUKS encryption entry, volunteers can pull builds via Koji and run regression suites to help validate hardware compatibility. The testing window closes September 5, after which QA engineers will determine if the kernel is ready for broader distribution across supported Fedora releases.

Fedora Kicks Off Community Test for Linux Kernel 7.2 This Week

Fedora 43 and 44 users can start pulling Linux kernel 7.2 into their systems. The Fedora QA team has scheduled a full week of community testing, running through September 5, to catch regressions and hardware gripes before the package hits stable repositories. Kernel 7.2 went upstream on August 16, which means Fedora is already two weeks ahead of the standard packaging window.

The changelog for 7.2 is long. If you run Btrfs, large folios are now enabled by default, which should meaningfully speed up filesystem operations for workloads that allocate in bigger chunks. AMDGPU gets HDMI 2.1 FRL support, so if you're pushing 4K120 or 8K60 over a single cable, the driver finally has a shot at it. There's also partial Apple M3 support, Cache Aware Scheduling for better task placement across CPU cache topologies, and another round of crypto hardening that finally nukes the strcpy API. Not bad for a point release.

Where 7.2 fits in the timeline

Kernel 7.0 shipped in April and died in June. 7.1 ran until mid-August. Now 7.2 is the current stable target, sitting alongside the 6.18 LTS branch that Greg Kroah-Hartman keeps alive through December 2028. The roughly two-month cycle isn't slowing down, which is why Fedora's testing cadence has to be so tightly synchronized. Keep in mind that while Torvalds owns the feature cycle, K-H is the one stamping security patches onto stable builds like 7.2.2.

Testing it yourself

Grabbing the kernel isn't a dnf update away yet. You'll need the koji CLI, a quick query to find the right build tag, and then dnf update kernel-7.2.2-*.rpm or rpm-ostree override replace if you're on Silverblue. The regression suite pulls from Pagure's kernel-tests repo, and you submit results directly to the Fedora QA page. There's a known bug right now, Bug 2441941, where the screen goes black right when you need to type your LUKS passphrase. The hardware configuration needed to reproduce it is still unknown, but the test day page is asking reporters to leave their GPU and motherboard specs on the tracker.

Justin Forbes and Augusto Caringi are packaging the kernel, while Adam Williamson, Lukáš Růžička, Kamil Paral, Petr Sklenář, and Jaroslav Groman are running point on QA. It's a tight group, and Fedora's testing philosophy means community volunteers do a lot of the heavy lifting. The matrix channel #kernel:fedoraproject.org is where the real-time conversation happens, and the Fedora test mailing list picks up the slack for async reporting.

The test week wraps September 5. If the regression count stays low and the hardware matrix holds up, expect 7.2 to land in Fedora updates within a week of the cutoff. As the official test day page puts it, "Exact reproducible steps (and whether re-runnable)" matter more than anything else when filing reports. Head here to submit bugs against the kernel component in Fedora Bugzilla, and drop your exact hardware, Fedora version, and kernel build number in the report. Reproducible steps beat vague complaints every time.

Head here for more information.