The Wire · Showcase
RUST TOOLCHAIN FIXES LAND, OMARCHY TACKLES SUSPEND RACE AND HARDWARE DETECTION
By RepoJournal · Filed · About Linux
Linus merged rust infrastructure updates and a cascade of subsystem fixes across firewire, LoongArch, and perf tooling, while the Omarchy team shipped five critical fixes addressing fingerprint reader false positives, zram configuration conflicts, and a dangerous screen-lock-to-suspend race condition.
The kernel took in zerocopy v0.8.54 to squash a modpost error under CONFIG_CC_OPTIMIZE_FOR_SIZE=y, fixing a toolchain pain point that was blocking smaller builds [1]. Perf tools synced kernel headers and cleaned up build artifacts [2], while the firewire subsystem patched a fragmented datagram reassembly bug in RFC 2734 IPv4 over IEEE 1394 that dropped packets across multiple buffer ranges [3]. LoongArch addressed kgdb, BPF JIT, and laptop driver issues alongside build warnings [4]. On the Omarchy side, the team fixed a false positive where the Synaptics vendor ID 06cb matched non-fingerprint devices, stopped prompting for fingerprint setup on machines without readers [5], and moved zram tuning to vendor drop-ins at /usr/lib/systemd/zram-generator.conf.d/ to avoid pacman file conflicts during package upgrades [6]. A critical fix reordered the Panther Lake kernel install before camera DKMS modules to cut redundant compilation work from 73 seconds down to single digits [7]. Most importantly, omarchy-sleep-lock now blocks suspend until the screen actually locks, closing a race where closing the lid could suspend with the session exposed when logind's InhibitDelayMaxSec timer expired before the lock service reported secure [8].
One email a day. Unsubscribe in one click.
Keep up with Linux in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.
One email a day. Unsubscribe in one click. Read a past issue →
Action items
- → Test zram drop-in migration on next Omarchy deployment to ensure no package conflicts basecamp/omarchy [plan]
- → Verify suspend-lock ordering on lid-close scenarios in Omarchy installs basecamp/omarchy [monitor]
- → Rebuild rust projects with CONFIG_CC_OPTIMIZE_FOR_SIZE if affected torvalds/linux [plan]
References
- [1] Merge tag 'rust-fixes-7.2-2' of git://git.kernel.org/pub/scm/linux/kernel/git/ojeda/linux torvalds/linux
- [2] Merge tag 'perf-tools-fixes-for-v7.2-1-2026-07-25' of git://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools torvalds/linux
- [3] Merge tag 'firewire-fixes-7.2-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394 torvalds/linux
- [4] Merge tag 'loongarch-fixes-7.2-1' of git://git.kernel.org/pub/scm/linux/kernel/git/chenhuacai/linux-loongson torvalds/linux
- [5] Stop offering fingerprint setup on machines with no reader basecamp/omarchy
- [6] Ship zram tuning as a vendor drop-in basecamp/omarchy
- [7] Swap the Panther Lake kernel in before the camera DKMS modules basecamp/omarchy
- [8] Lock the screen before suspend instead of racing logind for it basecamp/omarchy