"'Lots of features & bug fixes and hopefully on a few regressions. Big focus around latency and buffer depths, .e.g support for inflight on the client and in progress (per Little's Law) on the server.'"
#Linux#kernel 6.8.5, 6.6.26, 6.1.85, and 5.15.154 were released.
They among others contain the mitigations for the "native BHI (Branch History Injection)" hardware vulnerability that were mainlined yesterday[1] shortly after the vulnerability was published[2].
"The @KernelCI project is happy to announce the creation of a
Community Engagement Working Group (WG).
[…] connect with [#Linux] #kernel maintainers, discuss and improve test quality for their subsystems, help onboard new users to the project's systems and services, address their requirements, and act on feedback from existing users, fixing bugs, and implementing new features. As well as following up on regressions detected by KernelCI systems […]"
2/ Side note: /me wondered if the "this" in "WG communication will be looped into this maillist." contained a link that was lost in a translation to text mail or if it meant kernelci@lists.linux.dev (I assume the latter)
"'[…]this whole "nested LSM" stuff as a design goal just needs to be all rolled back, and the new design target is "one LSM, enabled statically at build time, without the need for indirect calls."
Because we're now in the situation where the security hooks are actually a source of not just horrible performance issues, but also actual insecurity[…]"'
I often wondered if SELinux would have become way easier to configure and manage quickly long ago, if we early on had deemed it as the the one and only to rule them all (aka the "highlander")
@torvalds@kernellogger@jarkko if tooling like ls could be allowed to break their defaults to let me see why tftpd can’t see the file I just copied from my home to /srv/ftp then sure.
(100% agree though on one to rule them all. So fed up with the current state of things in this domain)
Top-posting aka TOFU[1] on #LinuxKernel lists like #LKML? I have no big problem with that[2]. I even don't mind a HTML mail much.
But I'm having a really really hard time if people use email clients that do not properly quote mails when replying – like Microsoft 365 Outlook apparently does. 😠
@kernellogger What good would quote marks do when top-posting? Their whole purpose is to allow interleaving different levels of quotes in a discussion.
I'm not saying it's OK to violate the conventions of a community. If Outlook can't quote properly then it's not an adequate client for posting to LKML.
Valid point, but we have things like Syzbot or Regzbot that react to commands in mails ("#regzbot foo: bar"…). Such mails will make the bots execute the commands again, unless somebody teaches them to detect such cases automatically – which is hard, unless all such clients (in the long term there might be more) agree on on separator to clearly mark what's new and what's old.
"'"Recently news went around about explicit sync being merged into #Wayland protocols, and in the wake of that I saw a lot of people having questions about it, and why it was such a big deal… So here’s a short-ish explanation of what it is, why it’s needed and what the benefits are over the old model.
[…]why is it such big news then?
The answer is simple: The proprietary #NVidia driver doesn’t support implicit sync at all, […]"'"
"Man muss einsehen, dass wir - auch alle, die nicht daran beteiligt sein wollen - wirklich die Quellen des Geldes sind, das die Kriminalität finanziert"
"'"[…] a subsystem that was introduced in the #Linux 2.4 #kernel that provides a framework for implementing advanced network functionalities such as packet filtering, network address translation (NAT), and connection tracking. It achieves this by leveraging hooks in the kernel’s network code, which are the locations where kernel code can register functions to be invoked for specific network events. […]"'"
I thought the question "do we want to include #Linux#kernel drivers in the upstream #LinuxKernel even for hardware used exclusively within a company" had been answered with "yes, that's a good thing, we even encourage that, as everyone benefits" many years ago, but nevertheless it was discussed today again here: https://lore.kernel.org/all/Zg6Q8Re0TlkDkrkr@nanopsycho/
"Linus Torvalds is just a manager, just check #Linux' commit history, he hardly contributes any changes these days."
There is some truth in statements like that which one bumps into occasionally on the net. Nevertheless they are not drawing an accurate picture at all, as Linus is still heavily involved and every week or two influences development a great deal with insightful and technical contributions or patches.
@kernellogger that's what good managers do, actually... it's not a contradiction at all. the problem is that managers on top of so many people have no technical knowledge whatsoever because they also have to deal with stuff that a foss project doesn't directly have to.
A #Canonical employee reported some out-of-tree code broke after something internal was renamed recently in #Linux 5.15.y – and as expected was told this is no regression at all, as the #LinuxKernel does not have a binary kernel interface, nor does it have a stable kernel interface:
Christoph Hellwig in a reply also wrote: "given that Canonical ignores our #kernel licensing rules and tries to get away with it I'm not going to offer any help to Canonical at all."
2/ "Given that #Canonical ignores our #kernel licensing rules and tries to get away with it I'm not going to offer any help to Canonical at all."
If you wonder what this statement from esteemed #Linux developer Christoph Hellwig is about:
I'm not 100% sure, but I expect it's either the bundling of #Nvidia's proprietary kernel graphics driver module or the inclusion of the #openZFS#LinuxKernel modules in #Ubuntu - or more likely both.