@sourcejedi @sima Yeah, no blog posts, just loads of lkml emails over the years, sorry.

That machine that randomly reassigned PCI ids at boot time is no longer with me, but it was great for testing. I'm sure you can do the same with virtual machines these days, passing in different virtual pci devices to them.

Persistent naming is for userspace to handle, the kernel just uses "grab the next free number" as it's naming "policy" as that's all it can really do.

A new set of stable kernels

https://lwn.net/Articles/1002917/ #LWN

@vegard Does our current documentation not make this clear?

If not, patches welcome :)

"Free Copilot in your GitHub account" is the 2020s version of "Free U2 album on your iPod".

@vegard Yes, that would miss the normal "review all the stable commits" process. If you think there is a mainline-only commit that needs to have a CVE, please let us know at the cve@k.o address and we can assign it then.

But better yet, backport the fix to stable and it all happens automatically for you :)

@matttbe @kernellogger Maybe, maybe not. Please see my old post here: http://www.kroah.com/log/blog/2021/02/03/helping-out-with-lts-kernel-releases/ for what drives all of this (hint, people actually asking that they need it AND providing the help to make it possible.)

#Linux kernel version 4.19.y is EOL. 4.19.325 will be the final version. You can check your kernel version with `cat /proc/version`. If your system is running such an old LTS kernel, consider moving to one of the many newer LTS versions listed on kernel.org:

* 6.6
* 6.1
* 5.15
* 5.10
* 5.4

https://lore.kernel.org/all/2024120520-mashing-facing-6776@gregkh/

Can you find an ITW 0-day from crash logs? Project Zero finds out

https://googleprojectzero.blogspot.com/2024/12/qualcomm-dsp-driver-unexpectedly-excavating-exploit.html

The #LinuxKernel's stable team extended the support timeframe for #Linux 6.11 from four to five years:

https://www.kernel.org/releases.html

To quote @gregkh from https://git.kernel.org/pub/scm/docs/kernel/website.git/commit/?id=e6083565a79c3d711c1a76d9312b8c00e06b826b:

'" Bump 6.1.y support up to 5 years.

Giving people a chance to phase in the shorter lifespans, if at all possible. Hopefully this should help a bit.'"

#Kernel

are you a programmer? do you like heavy metal? would you like to be *really upset* by a music video?

do i have something for you.

https://www.youtube.com/watch?v=yup8gIXxWDU

@xexaxo We do have those devs, they are just very overworked :(

"I'm probably not alone in thinking that sometimes the compiler writers are doing their hardest to make life hard for people writing low level code." -- David Laight at: https://lore.kernel.org/r/344b4cf41a474377b3d2cbf6302de703@AcuMS.aculab.com

It's a fun thread, recommended for anyone who deals with compilers and trying to get them to do what you would think would be a "easy" thing to do and the hacks around them to get them to do that (hint adding "+ 0" to an expression tricks the compiler into doing what you meant it to do is usually a sign that something is wrong somewhere...)

"Census III of Free and #OpenSource Software: Application Libraries leans on more than 12M data points from security tools such as Black Duck, FOSSA, Snyk, and Sonatype, which have been deployed at more than 10k companies"

https://techcrunch.com/2024/12/04/linux-foundation-report-highlights-the-true-state-of-open-source-libraries-in-production-apps/ #cybersecurity

2/ Regarding the #Linux 4.19.y EOL, see also this nice and interesting farewell note from @gregkh:

https://lore.kernel.org/all/2024120520-mashing-facing-6776@gregkh/

'"[#LinuxKernel 4.19] had a good life, despite being born out of internal strife. […]

As a "fun" proof that this one is finished […] , I looked at the "unfixed" CVEs from this #kernel release. Currently it is a list 983 CVEs long, too long to list here. […]"'

The last 4.19.y kernel has been released:
https://lore.kernel.org/lkml/2024120520-preorder-untracked-6e5b@gregkh/T/

Please move to a more modern kernel if you are somehow still running this one, which I strongly would not recommend doing.

@pro @xav Yup!

@xav it has only been a few hours, no idea how even a single day would work yet...

New hardware showed up today, turns out Linux works just fine on it. Here's the 6.12.1 kernel running in Wayland.

Water bottle for scale.

Yeah, so I may have been bored in a meeting today...

https://mirrors.kernel.org/bogus

@monsieuricon Oh great, of course now this means I need to write a hampster_fs kernel module and get it merged, yet another thing to add to my TODO list...