@vbabka @lwn Sigh yes of course...I'm in an advanced state of missed-connection jet lag and really shouldn't be posting things to the net right now. Fixed ,thanks.

@hillu I guess they should have waited a few more minutes and they would have gotten there.

Debian issued a security advisory stating that "several vulnerabilities have been discovered in the Linux kernel:

https://lwn.net/Articles/1097401/

Here, evidently, "several vulnerabilities" means "1,313 CVE numbers".

I conclude that it is a bad sign when your airline sends you a cheery note asking if you have any data from Air Tags and the like that might give them a clue as to where your suitcase is.

(1/2) The dust has settled, the coffee cups are washed, but the good vibes are here to stay:

All the talk videos are online : https://www.youtube.com/playlist?list=PLEVVgAZOU9P8

The slides, with more landing over the next few days (some speakers are still polishing 😉) - check the schedule to catch it : https://kernel-recipes.org/en/2026/schedule/

The drawings from our amazing attendees (https://kernel-recipes.org/en/2026/attendees-sketches/) and speakers (https://kernel-recipes.org/en/2026/speakers-sketches/)

Tons of photos: https://kernel-recipes.org/en/2026/2026-speakers-on-stage/ and https://kernel-recipes.org/en/2026/in-the-room/

@ljs @monsieuricon Anybody can put together a documentation patch :)

What may also happen is that said text will be kept around and posted when the process starts next year.

@ljs @monsieuricon So, as you may know, I am on the MS program committee. Statements that you have been "blackballed" are not in any way helpful; nor are they true.

The selection is based on a number of factors; bringing in some new faces has been one of my foremost objectives every time I have helped with that process, and I have had some success there. But, in a meeting limited to 30 people, where you *have* to have the people who are central to the maintainership process, there will be limits on how many new faces there can be.

We did lose something when the larger kernel summit went away. That was really the only opportunity most developers ever had to sit in the same room with Linus and express their thoughts. But I don't think that model is ever coming back.

@ljs @monsieuricon Would you be willing to expound on what "the maintainer's summit thing" is? What do you think should be different there?

I'm calling the community for help. If you would like your voice heard at the Maintainer Summit, please contact me by e-mail (laurent.pinchart@ideasonboard.com) to share your opinions on AI usage in the Linux kernel. Unless you explicitly request to be named, I will strictly respect your privacy and anonymize all the feedback I receive before sharing it with kernel maintainers. Please don't wait until the last minute as the week leading to the summit will be very busy. (5/5)

This, evidently, is what I look like when giving a talk these days.

“Millions of people around the world will soon consider large models ‘hoovering up’ all their work to be an astonishing theft of unprecedented proportions,” an internal Microsoft document cited in the case read, adding “almost no one intended for content they created to be used in this fashion, nor are they compensated for its use.”

https://www.404media.co/doom-loop-openai-and-microsoft-admits-llms-are-destroying-the-web-and-built-on-theft/

@david_chisnall This actually aligns fairly well with how I've seen the kernel community deal with the GPL. @torvalds once gave me some real grief for suggesting in a talk that a bit more licensing-infringement litigation might be a good thing; his point was that exclusion from the community is a far more potent weapon.

And say what you will, but the kernel community has had a lot of success in (eventually) convincing companies to play along.

But yes, I don't think the GPL has a lot of force when it comes to keeping companies from using any project of mine in proprietary ways.

TRUTH!
#scifi #sciencefiction

RE: https://mastodon.social/@nixCraft/117241250895962141

Ok, genuinely, tech journalists need to investigate why so much money is being laundered into Omarchy. A bunch of slopware from a white supremacist does not deserve $18 million when real Linux projects have gone unfunded for years. There has to be something else going on here.

The US federal government, it seems, is worried that the Chinese are engaged in "distillation" from US large language models

https://media.defense.gov/2026/Sep/08/2003992823/-1/-1/1/CSA_CHINA_BASED_AI_COMPANIES_MALICIOUS_DISTILLATION_AGAINST_US.PDF

"China-based AI companies route distillation requests through multiple pathways to gain
unauthorized access, consequently violating U.S. AI companies’ terms of use."

I'm shocked that an AI company would do such a thing. Certainly no US-based AI company would route requests through multiple paths to gain access...right...?

I miss the old-fashioned FOSS drama, where if you knew someone’s three-letter initials and they were an asshole, you just called them an asshole or ignored them, and didn’t worry that (1) they were a vengeful billionaire and/or (2) that they represented the pending downfall of democracy

@alrj I am surprised that people seem to think I'm unaware of that. Seriously...I live in Boulder... my question is what they think a "hash collision" is.

Just got a nifty bit of spam from a bot claiming to represent Weedmaps (a site for people trying to find cannabis products). They were, it seems, much impressed by an LWN article on hash collisions and were wondering if we could find it in our hearts to mention them there.

I am still trying to understand just what a "hash collision" would mean in that context; perhaps I don't have enough weed in the house to obtain the necessary insight.

@etchedpixels @jwildeboer ...but definitely stopped LinuxCare... sometimes you *really* miss the window.

@gregkh @KernelRecipes Heh ... I have a similar plot from the 7.2 development-statistics article that I'm thinking of using...