When 'Idle' Isn't Idle: How a Linux Kernel Optimization Became a QUIC Bug

Cloudflare engineers stumbled upon a bug that sounds like a sysadmin joke: the Linux kernel decided a QUIC connection was 'just taking a nap' and sent it to the grave. In reality, the connection was actively transmitting data — just very efficiently.

It all comes down to an optimization that makes the kernel think a socket is idle if there are no system calls. QUIC, unlike TCP, can bypass system calls — data flows directly through userspace. So the kernel thought, 'Eh, if it's not bothering me, I can kill it.' And the connection dropped.

Cloudflare called this a 'death spiral': on reconnection, the kernel would kill it again, and so on endlessly. It's like your grandma turning off the Wi-Fi router at night to let it rest, then wondering why the internet doesn't work in the morning.

The patch has been sent to the kernel mainline. Developers are advised to update if they use QUIC and notice strange disconnections — maybe it's not your shaky architecture, but Linux just 'caring' about power saving.

METABYTE studio comment: We've also blamed our own code a couple of times, only to find the kernel was just 'helping' — in the spirit of 'I deleted your files so they wouldn't get in the way.' If your networks act up, maybe look into kernel depths before pointing fingers at devs.