@monsieuricon no, it was delayed a bit, came a full second later :)

"We are sending you your account credentials in an encrypted Microsoft Word file with the password sent separately."

— How to say you are a government agency without saying you are a government agency.

@mripard @kernellogger And look, it does, through the kernelci project! If companies really cared, they would provide developers and resources to work on kernelci more, I know they can always use the help to make it better.

@spbnick @kernellogger I have always wanted a good CI feedback loop, which is why I worked on pushing everyone to support kernelci, and kernelci is getting better, but is not quite there yet. Slowly it is getting there.

@Logical_Error What vendor isn't providing kernel source for their phone? I haven't seen that in a long time, except for some China-based non-name ones, and even then it's not too hard to find the source with a bit of searching. Now replacing the kernel on the device is a different story, good luck with that!

Sequentially in my feed: a toot about the Mars helicopter Ingenuity and its continued flying around, followed by a toot about Linux 4.14 reaching EOL.

Which reminds me, Ingenuity is running a 3.6 kernel. And it has the only excuse I can tolerate for having not been upgraded: it's on a different planet. ;)

The 4.14.y kernel tree is now end-of-life: https://lore.kernel.org/all/2024011046-ecology-tiptoeing-ce50@gregkh/

It's been a good 6 years, and it was a solid kernel version for its time, but anyone still using it should have moved off it a long time ago as it has been showing its age for quite a while.

UPDATE: Blijkt dat het artikel 73 al sinds 2013 vragen oproept.
Vandaag in het nieuws dat een AIVD agent meegeholpen zou hebben aan het saboteren van het Iraanse kernwapenprogramma. Dit lijkt me uitstekend. Maar politiek Den Haag schijnt van niets geweten te hebben. En dat zou best kunnen, want de AIVD en MIVD mogen agenten dingen laten saboteren zonder toestemming van minister of toetsingscommissie, en dat is raar:
https://berthub.eu/articles/posts/het-curieuze-artikel-73-aivd-mivd/

For those of you who remember stuxnet, more details about how the virus actually might have gotten into the system it was designed for has been disclosed thanks to the Volksrant:

https://www.volkskrant.nl/kijkverder/v/2024/sabotage-in-iran-een-missie-in-duisternis~v989743/

(disclaimer, yes, it's in Dutch, but tools like google translate work well on it, and no, my Dutch is not good enough to read it in the native form, still working on that, ik lees een beetje Nederlands.)

@vbabka @rostedt @qyousef exactly, I'll gladly take dependent patches like that, would prefer to in fact, makes it simpler for everyone involved.

@warthog9 Many thanks to you and
@monsieuricon 's work here and your continued work to keep vger alive all these years, it's one of the primary reasons that Linux development works so well.

Ok, Vger's MX is heading off to point to subspace on Thursday. Web services are staying put for now, so if you link to / use Vger it's staying put (possibly with a massive OS upgrade coming).

The fundamental infrastructure isn't going anywhere even if it has to change it's name, and should lists not want to head off to subspace, infradead, etc I've got https://vger.email up and running and capable of picking things up should anyone want to jump.

End of an era, Vger's been independent of kernel.org from it's start, but it's a non-trivial set of lists that literally keep the Linux kernel community moving, and has since it's inception. It's realistically needed an upgrade to deal with a plethora of problems, and frankly various large e-mail providers have made it nearly untenable to keep doing without it nearly being a full time job (at least at the scale that Vger's at)

It would be very silly to install and boot the stable kernel instead of the usual latest rc, just because it has some specific version number. But stable kernels need testing too!

Dirk: "Are you worried about bugs from LLM hallucinations getting into the #Linux kernel?" Linus: "Well I see all the bugs that come in without LLMs, and so, no I don't." (Paraphrasing the exchange)

Little known fact: first kernel releases were shipped via the postal service.

@oleksandr @kernellogger @vbabka You can't do that, as many many developers do not properly tag real bugfixes with cc: stable, which is why we now take anything with Fixes: on it, when they seem sane.

Again, the patch that caused you problems here was marked this way so that it did get some "soaking" in linux-next and and delayed the stable backport for a few weeks on purpose. It flowed into stable into the correct way, this is as designed.

Well, except for the breakage, but that's what normally happens with hardware, go blame the vendors for that :)

@oleksandr @kernellogger That commit was tagged that way so it would be properly backported, if it's buggy then please let the developers know about it!

@oleksandr What do you mean by "properly reviewed"? They have all passed the normal review process in that they are in Linus's tree. If they are good enough for the next release, why are they not good enough for the previous one?

And as always, reviews for things that you think should not be included are greatly appreciated, we can't do any of this without you!

If you enjoy the hairiest of bug hunts with a thrilling conclusion, this one is for you. The hunt and hair pulling:

https://lore.kernel.org/regressions/480932026.45576726.1699374859845.JavaMail.zimbra@raptorengineeringinc.com/

and the conclusion:

https://lore.kernel.org/regressions/1105090647.48374193.1700351103830.JavaMail.zimbra@raptorengineeringinc.com/

Hats off to Timothy for seeing this one through to completion!

So, you want to read LKML with Gmail (experimental, testers needed)

https://lore.kernel.org/workflows/20231115-black-partridge-of-growth-54bf2e@nitro/