Our first KernelCI hackfest has shown how new contributors can quickly reach some results and extend automated testing for the upstream Linux kernel: foundation.kernelci.org/blog/2021/06/2… Get ready for the next one! #linux #kernel #kernelci #automatedtesting

This was fun to work on last week with Jordy, there's still a lot more work to do to clean these up, if people want to help out!

What Kees said:

Excellent talk by Greg K-H on why cherry-picking #CVE fixes is stupid and does not actually fix your security issues nor your quality issues. He tells what to do instead, and I fully agree with that. #software #security #Linux youtube.com/watch?v=HeeoTE…

Latest toy, runs Linux, weighs 24kb and is the size of a TV with much less resolution. Writing bash scripts that make loud clicky noises is fun. Recommended.

As requested, board in action, showing latest kernel release numbers. Noise is very low, in reality is is much louder than this.

But what do I know...

Started using @tailscale today for my stable kernel build testing, and, um, it seemed too simple? Connections "just work"? Recommended, if only everything were this easy to use. (note, they are giving the LF a discount, but that had nothing to do with this recommendation)

Great news!

"[…] the #Linux #kernel community almost never declares specific changes as “security fixes” […] many bugfixes are only determined to be security related after much time […] keep users from getting a false sense of security […]" From Greg K-H in 2018: kroah.com/log/blog/2018/…

Great work by the VUSec team, and thanks for them getting the needed Linux kernel developers involved early on, fixes are all in Linus's tree now and will be in the next round of stable updates.

To quote my release announcement "All users must upgrade".

I too rely on this everyday, great tool!

This box showed up today! Need to "borrow" a monitor from my son's system and get it set up this weekend!

As it's a rainy Sunday in lots of Europe today, why not fill out a developer survey to pass the time: research.net/r/VLP8RST Yes, I know you all get at least one request a week for this, but hey, what's one more, and this one is sponsored by a lot of good .eu groups.

My talk a few weeks ago about Trust and the Linux Kernel (going into stuff about the umn.edu incident)

Reminder for #Linux developers: Use a "Cc: stable@..." tag in changes you want to see backported to stable and longterm #kernel series, as a "Fixes" tag is not enough (but nevertheless might do the trick). For details see this #lkml msg from Greg K-H: lore.kernel.org/lkml/YwZmu1ZTb…

"Let's put the tool in the kernel!" Seriously, this is cool stuff, great work, and someone needs to forward port KML to a newer release, 4.0 is just too old for new research...

In which I write a teeny-tiny bit of Go code to make the bash scripts I use for kernel maintenance work a small bit prettier...

3/ There as usual was not even a hint in the release announcement that these new #Linux #kernel releases were fixing any vulnerabilities, just the standard "All users of the […] series must upgrade." advice. If that's news to you, you might want to read kroah.com/log/blog/2018/…