@kernellogger@sven@vegard@monsieuricon The other thing is: Either make it official policy that you don't want to see any Links in the commit messages or just accept that some people do and some people don't. But if you make it a policy then document it somewhere, please.
@kernellogger@sven@vegard@monsieuricon and how a simple request did spiral into a philosophical discussion of this dimension is a bit beyond me as well. We could've just ended this with "I personally don't like the links. If others find them useful then great but please don't try to convince others to add them." End of story, everyone is happy and can move on.
but groff must be one of the original sins. Like, Moses came down from the mountain and was like "don't do groff" but accidently dropped the first stone table or something. Like seriously, everytime I have to look at patches I die a little inside.
I love how Apple will now be repeating every goddman security mistake by writing their own container runtime. I thought we're past all that but hey, let's have some more path lookup CVEs. @cyphar
I think we're slowly seeing the severe implications of AI coding slop creeping up. In the last 24 hours we have received a bunch of bug reports (against non-upstream kernels even) on fsdevel that are almost guaranteed to be generated by some bot.
In addition we seem to be getting really strange security@kernel.org reports that report normal system behavior as security vulnerabilities.
I've done a series that adds support for AF_UNIX sockets in coredumps. Userspace provides an AF_UNIX socket path via core_pattern and the kernel connects to it, shuts down the read side and writes the coredump to the socket.
This means no more super privileged usermode helper upcalls and makes for a very nice API experience. I captured coredumps simply via socat:
Oh yeah, I already mentioned this a while ago but I also added support for pidfds in Linux coredumps.
/proc/sys/kernel/core_pattern has been extended so userspace can instruct the kernel to install a pidfd for the crashing process into the usermode helper process, e.g., systemd-coredump.
Picked back up the work for VFS {g,u}id squashing. IOW, mapping all {g,u}ids down to a single {g,u}id. Any process that doesn't have that {g,u}id but is still privileged otherwise will write to disk as the squashed {g,u}id. I just finished a draft and selftests that miraculously work.
I've written a post that shows how to list all mounts in all mount namespaces (all mounts on the system) using new apis we added to the #vfs this year.