All microconferences (MCs) at LPC 2025 have been accepted! It is time to submit topics to your favorite MCs.
Please check out our latest blog post for the list of MCs, and how to create a ideal MC topic.
https://lpc.events/blog/current/index.php/2025/07/25/all-microconferences-have-been-accepted/
I've been playing with the LLM code assistants, trying to stress them out with the Linux kernel code. So far, I've had success with them writing reasonable unit tests:
https://lore.kernel.org/lkml/20250717085156.work.363-kees@kernel.org/
https://lore.kernel.org/lkml/20250724030233.work.486-kees@kernel.org/
These both saved me some time since it emitted quite a lot of good boundary testing code, but I had to massage them both a bit until I was happy with the coverage. But it was a net win on time spent.
And then I walked it through fixing a buffer overflow. This one didn't save me any time because I had to tell it how to look at the problem. Since it was a shorter/simpler session, I included my exact prompts just for anyone interested in what I did:
https://lore.kernel.org/lkml/20250724080756.work.741-kees@kernel.org/
This graph is the one I'm most excited about: the lifetime of security flaws in Linux is finally starting to get shorter (and the number of fixed flaws continues to rise).
https://hachyderm.io/@LinuxSecSummit@social.kernel.org/114750428620118674
Oh good, some undocumented (in fact - man page implies you CANNOT DO IT) mremap() behaviour that even I, who have rewritten the entirety of mremap() code missed... + then accidentally removed...
Tests and documentation incoming...
I got ask how to get into kernel development. Basically asking for a starting point to work (simple bugs etc). I don't know a good answer and kernelknewbies seems also pretty outdated. Any ideas?
In case you want to join my company (#SUSE), we're looking for an #infrastructure engineer!
#FediHire
https://suse.wd3.myworkdayjobs.com/Jobsatsuse/job/Czech-Republic-EMEA/Senior-Software-Engineer--Core-Platforms-_71006946