Hmm, seems[1] people submitting #Linux#kernel pull request in #github for torvalds/linux[2] do not get a helpful "you are wrong here" message[3] from the KernelPRBot any more.
Does anyone know if the service/the bot was abandoned? Or is it just broken?
[Edit] should be working again, see replies! [/Edit]
The Linux kernel include/linux/math.h header has macros
roundup(x, y)
and
round_up(x, y)
What do you think they do? Would you know the difference between the two without looking it up? What happens if you mix them up? How significant is the single underscore there?
Wait, what? Building #Linux now (e.g. since [1], which is in 6.10-rc1) requires #python[2]? At least when building the msm graphics driver? Uhh, interesting. 🧐
'"[…] I introduced that "no regressions" rule something like two decades ago, because people need to be able to update their kernel without fear of something they relied on suddenly stopping to work. […]"'
Follow the link for context and other statements that did not fit into a toot.
Documentation/process/stable-kernel-rules.rst[1] now mentions how to tag commits you do not want to see backported to stable/longterm series without an explicit request.[2]
Ohh, and it now mentions the difference between stable@kernel.org and stable@vger.kernel.org, too.[3]
The #CVE count of the #Linux#kernel is not looking good these days compared to any other #OS is it. Maybe time to switch to #FreeBSD or some other system which doesn't claim to find hundreds of significant vulnerabilities every day
“Building Bridges, Not Barriers: Embracing Upstream Support for Lasting Results“ (https://www.youtube.com/watch?v=zwyE44A9-8E) is an inspiring presentation from Texas Instruments. And it is spot on, here’s a picture of my TI OMAP3 IGEPv2 board (released in 2009) running the latest Linux mainline kernel.
Since I've migrated from screen to tmux years ago, I always felt that missed screen's excellent support for serial devices.
But recently I found https://github.com/tio/tio which was developed exactly with that use case in mind and I couldn't be happier. Such an amazing tool.
"'[…] #git was created as a tool to unblock future #Linux#kernel releases — not intended as a global reinvention of all source code management; Linus’s comments highlight that he explicitly saw source code management as the domain of other tools that would then interface with git. […]'"
Suggest some beginner-friendly resources for learning about Linux kernel features like LSM (SElinux, Yama Landlock, Lockdown), Netfilter, eBPF, Cgroups, Namespaces, and KVM :D
OK, I submitted an abstract for kernel summit track: "TPM2 story so far...". It would be from the angle of thinking it more like a protocol or contract that all kinds of hardware and TEE's can speak than just a chip per se...
Not that motivated to travel, so not a huge disappointment if not accepted :-) But yeah I have an angle and will prepare that one properly if accepted. So done my duty I guess at least...
'" The data shows that “frozen” vendor #Linux kernels, created by branching off a release point and then using a team of engineers to select specific patches to back-port to that branch, are buggier than the upstream “stable” Linux #kernel created by Greg Kroah-Hartman. '"
👀 PowerPC 40x Processor Support To Be Dropped From The Linux Kernel
— @phoronix
"Back in 2020 was a proposal for dropping PowerPC 40x support from the Linux kernel given that the code was orphaned for a long time with no apparent users. The PowerPC 40x processors were found in thin clients, set-top boxes, and other devices during the 90's. Finally now it looks like that the PowerPC 40x removal is set to happen"
Theo de Raadt and Linus Torvalds are debating mseal(), a #Linux variant of OpenBSD's mimmutable() syscall – which might or might not be merged for #kernel 6.10, as can be seen from other parts of the discussion: