Tootfinder

Wondering why my mainline-wo-mergew #Linux #kernel vanilla #copr for #Fedora 44 x86_64 already has …

Instead of a simple
`sudo dnf upgrade`
you now need something like
`sudo dnf --setopt=allow_vendor_change=1 upgrade $(rpm -qa --qf '%{name} \n' 'kernel*' 'libperf*' perf python3-perf rtla rv | sort -u)`
when enabling the #Linux #kernel vanilla …

Lunch was superb as usual - time for #Linux #kernel #security stuff now!
https://kernel-recipes.org/en/2026/schedule/linux-secure-by-default-are-we-there-yet/

Well, @… found #Linux #kernel and older doesn't do anything at all. I'm going to take an educated guess that 6.12 failed to build, but this didn't get our LLM backport experts to think that something is wrong and they just pushed it to 6.6 and older where it didn't fail to build.

Zero days since the #Linux #kernel made a security release of all branches, containing exactly one patch, except for 6.12 which was skipped for no clear reason, and there doesn't seem to be anything about that on the ml. And now I'm scratching my head if I should do a backport for #Gentoo, or wait for the release, or perhaps there was a good reason why the patch was added to every other LTS branch but not 6.12…