drgn 0.1.0 is out now! If you're a crash-utility holdout, try drgn's new crash compatibility mode. There are also big new features for built-in commands, searching memory, mapping code addresses to source locations, and over 80 new helpers. Thanks to everyone who pitched in. See more highlights here: https://drgn.readthedocs.io/en/latest/release_highlights/0.1.0.html and the full release notes here: https://github.com/osandov/drgn/releases/tag/v0.1.0.

Just posted my second LSF/MM/BPF topic proposal [1] for per-CPUs/threads/reads/writes access monitoring extension of DAMON. Please read my blog post [2] if you are interested in more contexts of the extension project.

[1] https://lore.kernel.org/20260218054320.4570-1-sj@kernel.org
[2] https://damonitor.github.io/posts/damon_cpus_write_monitoring_rfc_v3_plan/

#linux #kernel #damon #lsfmmbpf #numa_balancing

Another post in my series about the kernel CVE process, all about how we classify fixes to be assigned a CVE and other related things:

http://www.kroah.com/log/blog/2026/02/16/linux-cve-assignment-process/

Finally posted [1] the DAMON yearly retro for 2024, before the Lunar new year for 2026 in my time zone. ;)

To quote the summary:
"So, 2024 was a year DAMON has more publicly and widely adopted, and extended
itself for more use cases."

[1] https://lore.kernel.org/20260216210625.68098-1-sj@kernel.org

#linux #kernel #damon #2024 #yearly_retro

mirrors.kernel.org is down because it threw 2 disks in a RAID-6 array and then ground itself to a halt. I'm trying to resuscitate it. Please use mirrors.edge.kernel.org (it's pointing at our only remaining server that is now up, in Amsterdam).

We need more redundancy for these systems. After exiting Equinix, we are reduced to just 2 nodes (and hence, we're now down to 1 until I rebuild the RAID array on the one that's currently offline).

If you can donate us a server with at least 70TB of space and lots of bandwidth, I'd like to hear from you, but it has to come with hosting, as we don't have any physical datacentres any more and must rely on the kindness of strangers to host them.

Two LSF/MM/BPF related DAMON news.

1. I proposed [1] an LSF/MM/BPF session for discussing how production-level data access-aware transparent hugepages can be developed.

2. DAMON has nominated [2] as one of Linux kernel Machine Lerarning Library's demonstration targets.

[1] https://lore.kernel.org/20260211022845.68865-1-sj@kernel.org
[2] https://lore.kernel.org/c24a209d5a4af0c4cc08f30098998ce16c668b58.camel@ibm.com

#linux #kernel #lsfmmbpf

Since we’re not superstitious, the 13th edition of KR will take place September 21–23, 2026 (black cats strictly forbidden during this edition — even on a leash… 😄). We hope to see loads of you there!

And because we want to keep offering the best possible conditions for three days of good vibes and community for everyone, feel free to support this edition by becoming a sponsor. All the info is here!

https://kernel-recipes.org/en/2026/sponsor/

Dan Carpenter is looking for support for his ongoing bug-fixing work:

https://lwn.net/ml/all/caa37f28-a2e8-4e0a-a9ce-a365ce805e4b@stanley.mountain

He says: "The situation isn't great. The zero day bot can't do cross function analsysis and it only looks at checks with a low false positive rate. We're missing out on a bunch of bugs." *Not* missing those bugs sounds like it would be a good thing.

DAMON user-space tool (damo) will start supporting command line auto completion from next release. The next release will happen tomorrow. You can also try it right now on its development branch [1].

[1] https://github.com/damonitor/damo/tree/next

#linux #kernel #damon #damo #command_autocompletion

korgalore demo: yanking arbitrary lore.kernel.org threads into generic gmail

https://youtu.be/wOi_qHSO7KY

Once again there's a kernel developer position open in the SUSE Labs Kernel Core team I'm part of! https://suse.wd3.myworkdayjobs.com/en-US/Jobsatsuse/job/Czech-Republic-EMEA/Linux-Kernel-Generalist_71007379

So @lwn is currently under the heaviest scraper attack seen yet. It is a DDOS attack involving tens of thousands of addresses, and that is affecting the responsiveness of the site, unfortunately.

There are many things I would like to do with my time. Defending LWN from AI shitheads is rather far from the top of that list. I *really* don't want to put obstacles between LWN and its readers, but it may come to that.

(Another grumpy day, sorry)

""News: this is my last linux-next release. Mark should start doing these soon."" – Stephen Rothwell in https://lore.kernel.org/linux-next/20260115161417.5a82a41c@canb.auug.org.au/

Reminder, Stephen announced that he would be stepping down a few weeks ago[1]]

Many many thanks, Stephen, for all your work over nearly 18 years[2], much much appreciated!

And thanks @broonie for picking up this thankless task!

[1] https://hachyderm.io/@kernellogger/115739700056940486

[2] Tue, 12 Feb 2008 – Announce: Linux-next (Or Andrew's dream :-)) – https://lore.kernel.org/all/20080212120208.f7168a91.sfr@canb.auug.org.au/

#linux #linuxnext #LinuxKernel #kernel

So somebody took a couple of LWN's recent conference articles, threw them into an LLM blender with some other stuff, and produced ... this ...

https://www.webpronews.com/linux-kernels-future-tab-integrates-rust-navigates-ai-boosts-collaboration/

Google News propagates that stuff - something they have long refused to do with LWN's original material. But somehow we're supposed to continue to exist to feed material into that machine?

Sorry, having a grumpy day.

RE: https://mastodon.social/@brauner/115871045863565861

Be sure to request an invite to #lsfmmbpf 2026 in Zagreb, Croatia!

DAMON user-space tool v3.0.9 and later supports recording data access pattern on Android. Kudos to @rostedt since this change was inspired from a chat that I had with him at LPC'25.

[1] https://damonitor.github.io/posts/damo_support_trace_cmd/

#linux #kernel #damon #damo #trace-cmd #android

Another post in my Linux kernel CVE process series, "How the Linux kernel security process works": http://www.kroah.com/log/blog/2026/01/02/linux-kernel-security-work/

Time to look back 2025.

In 2025, I made 2nd and 1st biggest changes to Linux kernel memory management subsystem among the 321 people, in terms of lines of changes (6,661 / 73,685 lines) and commits (199 / 1,870 commits).

For the Linux kernel whole tree, the numbers become 71-st (11,362 / 4,809,577 lines) and 25th (333 / 75,462 commits) among 5,637 people.

For open source projects other than Linux, I made around 564,210 lines of changes with around 2,157 commits.

For more details of the stats and how it was made, refer to https://sjp38.github.io/posts/my_opensource_commits_stat_2025/

#2025 #commits #statistics #linux #kernel #damon #memory_management

GPLv2 affirmation…

I don’t generally post here as people have probably noticed, but here’s a pdf of a recent court ruling, and this turns out to be the easiest way for me to link to a copy of it, since I don’t really maintain any web presence normally and I don’t want to post pdf’s to the kernel mailing lists or anything like that.

And the reason I want to post about it, is that it basically validates my long-held views that the GPLv2 is about making source code available, not controlling the access to the hardware that it runs on.

The court case itself is a mess of two bad parties: Vizio and the SFC. Both of them look horribly bad in court - for different reasons.

Vizio used Linux in their TVs without originally making the source code available, and that was obviously not ok.

And the Software Freedom Conservancy then tries to make the argument that the license forces you to make your installation keys etc available, even though that is not the case, and the reason why the kernel is very much GPLv2 only. The people involved know that very well, but have argued otherwise in court.

End result: both parties have acted badly. But at least Vizio did fix their behavior, even if it apparently took this lawsuit to do so. I can’t say the same about the SFC.

Please, SFC - stop using the kernel for your bogus legal arguments where you try to expand the GPLv2 to be something it isn’t. You just look like a bunch of incompetent a**holes.

The only party that looks competent here is the judge, which in this ruling says

Plaintiff contends the phrases, “machine-readable” and “scripts used to control compilation and installation” support their assertion in response to special interrogatory no. 4 that Defendant should “deliver files such that a person of ordinary skill can compile the source code into a functional executable and install it onto the same device, such that all features of the original program are retained, without undue difficulty.”

The language of the Agreements is unambiguous. It does not impose the duty which is the subject of this motion.

Read as a whole, the Agreements require Vizio to make the source code available in such a manner that the source code can be readily obtained and modified by Plaintiff or other third parties. While source code is defined to include “the scripts used to control compilation and installation,” this does not mean that Vizio must allow users to reinstall the software, modified or otherwise, back onto its smart TVs in a manner that preserves all features of the original program and/or ensures the smart TVs continue to function properly. Rather, in the context of the Agreements, the disputed language means that Vizio must provide the source code in a manner that allows the source code to be obtained and revised by Plaintiff or others for use in other applications.

In other words, Vizio must ensure the ability of users to copy, change/modify, and distribute the source code, including using the code in other free programs consistent with the Preamble and Terms and Conditions of the Agreements. However, nothing in the language of the Agreements requires Vizio to allow modified source code to be reinstalled on its devices while ensuring the devices remain operable after the source code is modified. If this was the intent of the Agreements, the Agreements could have been readily modified to state that users must be permitted to modify and reinstall modified software on products which use the program while ensuring the products continue to function. The absence of such language is dispositive and there is no basis to find that such a term was implied here. Therefore, the motion is granted.

IOW, this makes it clear that yes, you have to make source code available, but no, the GPLv2 does not in any way force you to then open up your hardware.

My intention - and the GPLv2 - is clear: the kernel copyright licence covers the software, and does not extend to the hardware it runs on. The same way the kernel copyright license does not extend to user space programs that run on it.

Together with my LPC videos [1], the video of my OSSummit Japan for a kernel development mailing tool (hkml) that I develop for myself and the community is also up on Youtube [2].

[1] https://social.kernel.org/notice/B1QVooy6voIN85T33I
[2] https://youtu.be/f09kvPvYMsM?si=EXUiMTrZSpwTXMGy

#ossummit #linux #kernel #hkml