Linux Kernel Daily: The RC4 Cleanup Sweep

Linus pulled six subsystem fix branches into 7.2-rc4, with block and RISC-V carrying the heaviest fix loads. The common thread is edge-case hardening — race conditions, uninitialized reads, and use-after-free bugs — rather than new features, exactly what you want to see this late in a release cycle.

Duration: PT2M22S

Episode overview

This episode is a short developer briefing from Linux Kernel Daily.

It explains recent repository work in plain language.

  • Show: Linux Kernel Daily
  • Published: 2026-07-20T06:01:20Z
  • Audio duration: PT2M22S

Transcript excerpt

This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.

Good evening. It's July 20th, 2026, and this is Linux Kernel Daily.

Tonight's story is release discipline. With 7.2-rc4 now tagged in commit 1590cf0, every merge that landed today was a fix, not a feature — and the pattern across them is edge-case correctness.

Start with block, the biggest batch from Jens Axboe in commit 980ab36. Several of these are genuine race and lifecycle bugs: a race in blk time get nanoseconds that could silently return zero, a radix tree insertion failure in blk cgroup leaking state, and loop device detach leaving dead partition devices behind…

IO-uring, in commit a2b81de, tells a similar story at the security boundary. A use-after-free was possible if the same BPF ops map got registered twice, and a follow-up fix closes a dangling-buffer path in the provided-buffer grow logic — worth remembering if you're tracking that feature, since this is a second pass…

RISC-V, in commit 82a4758, rounds out the theme with memory-safety cleanup: an uninitialized read in hwprobe get CPUs, and a cache-flush ordering fix in sparse vmemmap that prevents spurious faults on certain microarchitectures. That vmemmap fix is notable because it's not RISC-V-specific — it touches…

Small…

Nearby episodes from Linux Kernel Daily

  1. Weekly Recap - Late-Cycle Fixes Across Storage, Graphics, and Security
  2. Late-Cycle Fixes Converge on Resource Leaks and Error Handling
  3. Display Fixes and a Hidden Security Cleanup
  4. Late Cycle Fixes Converge on Data Integrity
  5. Testing Infrastructure Cleanup
  6. Late-Cycle Fixes Land in Sound and Btrfs
  7. The RC3 Cleanup Wave
  8. Weekly Recap - Stabilizing the 7.2 Release Cycle