Linux ThinkPad Driver Ready For Reporting Damage Device - Starting With Bad USB-C Ports
Queued yesterday into the platform-drivers-x86.git’s “for-next” branch are the patches for the Lenovo ThinkPad ACPI driver to begin reporting damaged device detection. This code being in the “for-next” branch makes it material for the next version of the Linux kernel and initially will be able to report to the user on damaged USB-C ports… ⌘ Read more

Linux 7.0 Looks To Enable Intel TSX By Default On Capable CPUs For Better Performance
A patch queued up into tip/tip.git’s x86/cpu Git branch ahead of the upcoming Linux 6.20~7.0 kernel cycle enables the Intel Transactional Synchronization Extensions (TSX) functionality by default on the mainline kernel for capable CPUs and those not affected by side-channel attacks due to TSX Async Abort (TAA) and similar vulnerabilities. For newer Intel CPUs with safe TSX support, this change can mean better performance with … ⌘ Read more

Intel Panther Lake GSC Firmware Published Ahead Of Laptop Availability
While Intel has been upstreaming various Panther Lake firmware bits to linux-firmware.git for pairing with their open-source kernel drivers ahead of Core Ultra Series 3 laptops shipping, one piece of the puzzle only published today is the GSC firmware for the Panther Lake graphics… ⌘ Read more

How Long Does It Take to Fix Linux Kernel Bugs?
An anonymous reader shared this report from It’s FOSS:

Jenny Guanni Qu, a researcher at [VC fund] Pebblebed, analyzed 125,183 bugs from 20 years of Linux kernel development history (on Git). The findings show that the average bug takes 2.1 years to find. [Though the median is 0.7 years, with the average possibly skewed by “outliers” discovered after years of hiding.] The longes … ⌘ Read more

https://git.laidback.moe/YakumoLabs/user_external/commit/b86ecbfc99a2f072f08f09eacbcf7d74ee23785e

@prologic@twtxt.net

Shin'ya M. > ./bin/mu
panic: native backend does not support syscall platform netbsd/amd64

goroutine 1 [running]:
git.mills.io/prologic/mu/internal/native/arm64.init.0()
        /home/shinyoukai/mu/internal/native/arm64/emitter.go:45 +0x7bf

…that was supposed to be the interpreter?

Valve & AMD Developers Delivered The Most Code Contributions To Mesa In 2025
A developer from Valve working on the RADV Vulkan driver was once again the most prolific contributor to Mesa in 2025 followed by AMD’s Marek Olšák with continued improvements around RadeonSI and Gallium3D… ⌘ Read more

Linux 6.19 Lands Fix For Dead WiFi With MediaTek MT792x Wireless
Merged to Linux Git on New Year’s Eve was a fix in the form of a code revert for broken MediaTek WiFi on the in-development Linux 6.19 kernel… ⌘ Read more

Hmmm 🤔

Excluding merges, 1 author has pushed 171 commits to main and 175 commits to all branches. On main, 294 files have changed and there have been 52880 additions and 18269 deletions.

From the Mu (µ) Gitea Activity Tab

@shinyoukai@neko.laidback.moe We finally abandoned our GitLab. I publicly mirrored my code in the Mills Data Center a few days ago: https://git.mills.io/lyse/tt2

Some Meaningful Performance Benefits For Clang + LTO Built Linux Kernels
Over the past few years building the Linux kernel with Clang has matured a lot thanks to upstream improvements to both LLVM/Clang and the Linux kernel. As it’s been a while since our last comparison for GCC vs. Clang built kernels on the resulting system performance, our latest year-end 2025 benchmarking is providing a fresh look at the Linux 6.19 upstream Git kernel built under the latest stable GCC 15 and LLVM Clang 21 compilers. Plus … ⌘ Read more

@shinyoukai@neko.laidback.moe Because you might not want to commit all changed files in a single commit. I very often make use of this and create several commits. In fact, I like to git add --patch to interactively select which parts of a file go in the next commit. This happens most likely when refactoring during a feature implementation or bug fix. I couldn’t live without that anymore. :-)

If you have a much more organized way of working where this does not come up, you can just git commit --all to include all changed files in the next commit without git adding them first. But new files still have to be git added manually once.

Why the hell do I have to git add everything!? Is it not enough for the file(s) to be already checked in from the get go?

Git = G(od damn)it

Everything about the future is classified information

https://git.laidback.moe/shinyoukai/mikuru

New Intel Xe3_LPD Firmware Binaries For Linux Ahead Of Panther Lake Laptops Launching
Ahead of Intel Core Ultra “Panther Lake” laptops expected to be showcased in just over one week at CES in Las Vegas, new Xe3_LPD firmware binaries were upstreamed today to linux-firmware.git in getting ready that production-ready support for Intel Panther Lake on Linux… ⌘ Read more

Qualcomm’s Xqci RISC-V Extension Now Deemed Non-Experimental For LLVM 22
In LLVM Git yesterday for next year’s LLVM 22 release the Qualcomm Xqci RISC-V vendor extension is no longer deemed experimental… ⌘ Read more

Intel NPU Firmware Published For Panther Lake - Completing The Linux Driver Support
Ahead of Intel Panther Lake laptops expected to debut next month at CES in Las Vegas, the Linux driver support for the next-gen “50xx” NPU of Panther Lake is now complete. The last piece of the driver support puzzle is now in place with the NPU firmware binaries having been upstreamed today to the linux-firmware.git repository… ⌘ Read more

I just had a closer look at https://git.mills.io/prologic/mu and it motivated me to do some compiler building myself again. Hopefully, I find some time in the next free days. I’m bad at it, but it’s always great fun.

@movq@www.uninformativ.de @kiwu@twtxt.net it just so happens to be a happy coincidence that I’m extending mu’s capabilities to now include a native toolchain-free compiler (doesn’t rely on any external gcc/clang or linkers, etc) that lowers the mu source code into an intermediate representation / IR (what @movq@www.uninformativ.de refers to as “thick layers of abstractions”…) and finally to SSA + ARM64 + Mach-O encoder to produce native binary executables (at least for me on my Mac, Linux may some later?) 🤣

Yet another free software web git interface going behind a paywall thanks to all the “AI bots” trying to kill the small web. Just great.

I cleaned up all my of AoC (Advent of Code) 2025 solutions, refactored many of the utilities I had to write as reusable libraries, re-tested Day 1 (but nothing else). here it is if you’re curious! This is written in mu, my own language I built as a self-hosted minimal compiler/vm with very few types and builtins.

https://git.mills.io/prologic/aoc2025

Early Linux 6.19 Benchmarks On AMD EPYC 9965 2P Excelling For AI & HPC Performance
As the Linux 6.19 merge window winded down this weekend, I began running this development kernel on more systems. While there are some scheduler regressions currently with Linux 6.19 Git, for HPC workloads especially I am seeing some encouraging results using a flagship AMD EPYC 9965 2P server configuration. ⌘ Read more

AMD ROCm’s TheRock 7.10 Released
TheRock is an interesting open-source build platform for ROCm and HIP that has taken shape over the past year. It’s become an official ROCm effort albeit still in early stages and relying on community contributions for enhancements for different consumer GPU targets and more. To date its users have largely relied on running the latest TheRock Git while today TheRock v7.10 was tagged… ⌘ Read more

Scheduler Woes: Bisecting Early Performance Regressions Found In Linux 6.19
Yesterday I noted some early performance regressions I’ve found on the Linux 6.19 kernel compared to Linux 6.18 LTS stable. Those initial benchmarks were on an AMD EPYC server. Since then I’ve seen many of the same workloads regressing similarly on an AMD Ryzen Threadripper workstation between Linux 6.18 and Linux 6.19 Git. Given the significant impact and AMD Threadripper processors always helping out to speed-up Linux kernel build time … ⌘ Read more

Early Benchmarks Of Linux 6.19 Git Showing Some Concerns
While just half-way through the Linux 6.19 merge window, over the weekend I began running some benchmarks of the current Linux 6.19 Git state compared to Linux 6.18 LTS stable. There are some minor performance improvements to note in a few of the tests on the first system I tested but also some regressions at this very early pre-RC1 state of the Linux 6.19 kernel… ⌘ Read more

@lyse@lyse.isobeef.org My theory is that these people simply don’t do “code archeology”. When something breaks, they don’t reach for git log. They simply don’t experience the pain that comes with bad commits / commit messages.

Or is that different in your company? 😅

@shinyoukai@neko.laidback.moe @prologic@twtxt.net Maybe that is helpful to you: https://git.mills.io/yarnsocial/twtxt2html/issues/12#issuecomment-20792

Yo @prologic@twtxt.net, apparently even ‘git clone’ is getting blocked by your Gitea or something (I’m using authentication, naturally)

@bender@twtxt.net yeah, I’ve been reading through the documentation last night and it felt overwhelming for a minute… +1 point goes to GTS’s docs. but hey, I’ll be taking the easy route: podman-compose up -d they provide both a container image and an example compose file in a separate git repo but I’m wondering why that is not mentioned anywhere in the docs, (unless it is and I haven’t seen it yet)

@itsericwoodward@itsericwoodward.com Nice to see someone else also participating! 🥳

(Btw, they don’t want us to share our inputs: https://www.reddit.com/r/adventofcode/wiki/faqs/copyright/inputs/ Yeah, it’s a bit annoying. I also have to do quite a bit of filtering on my repo …)

Working on day 3 of the Advent of Code 2025: https://adventofcode.com/

My solutions repo: https://git.itsericwoodward.com/eric/aoc-2025

Scoped User Access In Linux 6.19 To Reduce Speculation Barriers & Its Performance Hit
Merged yesterday to the Linux 6.19 Git codebase was the “core/uaccess” pull that introduces new scoped user-mode access with auto-cleanup functionality. This can reduce the number of speculation barriers encountered when needing to access user-mode memory and thereby avoiding some of the performance penalties incurred by speculation barriers… ⌘ Read more

Intel LASS, SGX EUPDATESVN & Microcode Staging Features Land In Linux 6.19
In addition to new AMD CPU features being merged today for Linux 6.19, there are also some new Intel CPU features that hit Linux Git today that are worth highlighting… ⌘ Read more

AMD Zen 6 RAS Preparation, AMD SDCI Features Merged For Linux 6.19
Linus Torvalds just merged another set of pull requests to Git for the in-development Linux 6.19 kernel. With the latest round of merges, there are two separate AMD changes worth highlighting… ⌘ Read more

Important Performance Work: Overhaul Of RSEQ & CID Management Merged For Linux 6.19
An important set of patches were just merged a few minutes ago to Linux Git for the ongoing Linux 6.19 kernel with some important performance implications… ⌘ Read more

gitlog-vim a wrapper to view git logs without plugins ⌘ Read more

HACK: vim using terminal app window panes and git repo aware viminfo contexts ⌘ Read more

Broadcom “BNG_RE” Next-Generation RoCE Driver Slated For Linux 6.19
Queued up via the Linux kernel’s RDMA development Git tree is “BNG_RE” as the next-generation RoCE driver from Broadcom… ⌘ Read more

@prologic@twtxt.net Your gitea thinks the LICENSE file in the yarn repository is SSPL-1.0 instead of GNU AGPL 3.0,
and I can’t help but giggle at that

The funny thing is, Yarn moving to Twt Hash v2 sounds a tad more optimistic than Git adopting SHA-256.

Git is several years too late, while Yarn is pretty much on time.

Speaking of WAF(s) / Web Applicaiton Firewalls – I actually had forgotten that not only have I designed a new WAF from scratch, but I’ve actually implemented it already, and done some local testing. I just haven’t put it into production yet… What od you think @aelaraji@aelaraji.com ? 🤔 https://git.mills.io/prologic/caddy-waf

@prologic@twtxt.net I originally did that, then I git reset XD

Tired to re-enable the Ege route to git.mills.io today (after finishing work) and this is what I found 🤯 Tehse asshole/cunts are still at it !!! 🤬 – So let’s instead see if this works:

$ host git.mills.io 1.1.1.1
Using domain server:
Name: 1.1.1.1
Address: 1.1.1.1#53
Aliases:

git.mills.io is an alias for fuckoff.mills.io.
fuckoff.mills.io has address 127.0.0.1

PS: Would anyone be interested if I started a massive global class action suit against companies that do this kind of abusive web crawling behavior, violate/disregards robots.txt and whatever else standards that are set in stone by the W3C? 🤔

Oh fuck me! I had basically turned off the route to git.mills.io last night and went ot bed at ~2AM after unsuccessfully trying to control the attacks (bad bots) that were behaving like a DDoS attack. Tried to re-enable the route this monring and *BOOM, they’re back! As-if they never stopped?! what da actual fuq?! Anyone have any clever ideas of what I can do here to allows normal users, like you nice folk and block ths obnoxious traffic?!

Fark me again with the bots. This time DDoS-style crawling from hundreds of IPs and dozens of ASN(s) wtf?!
I’ve had to disale the Ingress to my Git instance for the time being, i need to sleep and I can’t fight this :/

Hm, so regarding the hash change:

https://git.mills.io/yarnsocial/twtxt.dev/pulls/28

How about 2026-03-01 00:00:00 UTC as the cut-off date? 🤔

Linux 6.18-rc7 Released With Late Hardware Improvements
Linux 6.18-rc7 just arrived in the Git tree as the newest weekly test build leading up to Linux 6.18 stable hopefully debuting next Sunday, 30 November… ⌘ Read more

6.18-rc7: mainline
Version:6.18-rc7 (mainline)Released:2025-11-23Source:linux-6.18-rc7.tar.gzPatch:full ( incremental) ⌘ Read more

All my newly added test cases failed, that movq thankfully provided in https://git.mills.io/yarnsocial/twtxt.dev/pulls/28#issuecomment-20801 for the draft of the twt hash v2 extension. The first error was easy to see in the diff. The hashes were way too long. You’ve already guessed it, I had cut the hash from the twelfth character towards the end instead of taking the first twelve characters: hash[12:] instead of hash[:12].

After fixing this rookie mistake, the tests still all failed. Hmmm. Did I still cut the wrong twelve characters? :-? I even checked the Go reference implementation in the document itself. But it read basically the same as mine. Strange, what the heck is going on here?

Turns out that my vim replacements to transform the Python code into Go code butchered all the URLs. ;-) The order of operations matters. I first replaced the equals with colons for the subtest struct fields and then wanted to transform the RFC 3339 timestamp strings to time.Date(…) calls. So, I replaced the colons in the time with commas and spaces. Hence, my URLs then also all read https, //example.com/twtxt.txt.

But that was it. All test green. \o/

And regarding those broken URLs: I once speculated that these bots operate on an old dataset, because I thought that my redirect rules actually were broken once and produced loops. But a) I cannot reproduce this today, and b) I cannot find anything related to that in my Git history, either. But it’s hard to tell, because I switched operating systems and webservers since then …

But the thing is that I’m seeing new URLs constructed in this pattern. So this can’t just be an old crawling dataset.

I am now wondering if those broken URLs are bot bugs as well.

They look like this (zalgo is a new project):

https://www.uninformativ.de/projects/slinp/zalgo/scksums/bevelbar/

When you request that URL, you get redirected to /git/:

$ curl -sI https://www.uninformativ.de/projects/slinp/zalgo/scksums/bevelbar/
HTTP/1.0 301 Moved Permanently
Date: Sat, 22 Nov 2025 06:13:51 GMT
Server: OpenBSD httpd
Connection: close
Content-Type: text/html
Content-Length: 510
Location: /git/

And on /git/, there are links to my repos. So if a broken client requests https://www.uninformativ.de/projects/slinp/zalgo/scksums/bevelbar/, then sees a bunch of links and simply appends them, you’ll end up with an infinite loop.

Is that what’s going on here or are my redirects actually still broken … ?