Latest Linux and open source news from around the web

Docker Deep Dive Sponsored · View on Amazon → YubiKey 5 NFC Security Key Sponsored · View on Amazon →
Phoronix

ARCTIC Cooling Publishes ARCTIC Fan Controller Driver For Linux

A Linux driver has been published for the ARCTIC Fan Controller to be able to read fan speeds under Linux as well as setting the PWM fan speed for each of the ten fans supported by this controller. Making this driver all the more exciting is that ARCTIC Cooling is directly working on this driver rather than just being a community/third-party creation. Furthermore, ARCTIC Cooling is working on getting this driver to the upstream Linux kernel...

OMG! Ubuntu

GIMP 3.2 issues third release candidate with fresh fixes

GIMP 3.2 RC3 is now available for testing, giving those interested in trying the image editor’s upcoming features, the chance to do so. This is the third (and likely final) release candidate before the stable GIMP 3.2 release arrives. It’s said to deliver “a number of bug fixes and final polishes” to the many new features added in the development and beta builds. The changes mentioned below are from between RC2 to RC3, not from GIMP 3.0 to GIMP 3.2. If you’ve not tracked development, don’t think that what follows is an overview of what’s new in GIMP 3.2 as […]

LWN.net

[$] The ongoing quest for atomic buffered writes

There are many applications that need to be able to write multi-block chunks of data to disk with the assurance that the operation will either complete successfully or fail altogether — that the write will not be partially completed (or "torn"), in other words. For years, kernel developers have worked on providing atomic writes as a way of satisfying that need; see, for example, sessions from the Linux Storage, Filesystem, Memory Management, and BPF (LSFMM+BPF) Summit from 2023, 2024, and 2025 (twice). While atomic direct I/O is now supported by some filesystems, atomic buffered I/O still is not. Filling that gap seems certain to be a 2026 LSFMM+BPF topic but, thanks to an early discussion, the shape of a solution might already be coming into focus.

LWN.net

Høiland-Jørgensen: The inner workings of TCP zero-copy

Toke Høiland-Jørgensen has posted an overview of how zero-copy networking works in the Linux kernel. Since the memory is being copied directly from userspace to the network device, the userspace application has to keep it around unmodified, until it has finished sending. The sendmsg() syscall itself is asynchronous, and will return without waiting for this. Instead, once the memory buffers are no longer needed by the stack, the kernel will return a notification to userspace that the buffers can be reused.