Tootfinder

The full Weekend Reads report is on vacation this week, it will return next week. But we don't want to leave you with nothing. Here is one piece that might have made it into the top 5:
* The Input Stack on Linux
https://venam.net/blog/unix/2025/11/27/input_device…

The Input Stack on Linux
Let's explore and deobfuscate the input stack on Linux. Our aim is to understand its components and what each does. Input handling can be divided into two parts, separated by a common layer. We’ll try to make sense of all this, one thing at a time, with a logical and coherent approach.

Spent way too much time chasing some confusing segfaults before realizing that I was 4-byte offsetting and aligning my stack pointer out of habit.
On aarch64.

Weekend Reads
* How Quake got its TCP/IP stack
https://fabiensanglard.net/quake_chunnel/index.html
* MENOG 25 region advancement report

Stack Exchange is basically dead, I won't miss it but do think its a bit sad.
Graph is questions per month

Well this is interesting.
I've successfully determined which core is active. Core 1 correctly takes the branch, loads a valid initial stack pointer, and jumps into the infinite loop I wanted it to.
Core 0, on the other hand, crashes when doing basically the same instructions. Weird.