#Linux 6.7.12 is out, which is the "LAST 6.7.y #kernel to be released. This branch is now end-of-life. Please move to the 6.8.y branch at this point in time."
"I spotted that FPS was around 122 in the Shadow of the Tomb Raider benchmark at commit f6cef5f8c37f but after moving to commit 4ae3dc83b047 ("ALSA: timer: Fix missing irq-disable at closing") it decreased to 84".
"'"Neither snow nor rain nor heat nor gloom of night stays kernel rc releases.
Nor does Easter.
So here we are. Another week has passed, and rc2 is out. Nothing here look all that remarkable, and the fixes are fairly evenly spread out (so mostly drivers, because that's the bulk of the code).
Lasse Collin's patch-series updating the #LinuxKernel's #xz code that a few days ago hit #linux-next was dropped for now until backdooring of upstream xz is understood better:
Google has introduced Kernel Address Sanitizer (KASan) to enhance the security of Android firmware. KASan is designed to detect memory corruption vulnerabilities and stability issues before they affect user devices. It works by monitoring memory access operations to ensure they only target valid regions, identified in a shadow memory area. This tool has already helped identify and fix over 40 memory safety bugs in Android firmware. KASan is particularly useful for bare-metal targets, requiring specific compiler options and strategies to implement effectively. It's part of Google's efforts to address the security challenges posed by the vast number of Android devices and the fragmented ecosystem that makes vulnerability patching difficult.
If commands in a how-to do not work and no one reports it, does it have an impact?
The 'cloning #Linux from a #Git bundle' instructions[1] on #kernel.org were kinda broken for years: they until a few hours ago[2] contained a step to verify the bundle, which only worked if your working directory was part of a git repository.
Does that mean that nobody followed that how-to? Or that those who encountered the problem did not report it? 🤨 🧐
How do you explain the #Linux#Kernel to a kid? I found this graphic by Shmuel Csaba Otto Traian (CC BY-SA 3.0) on the Wikipedia page for Virtual Reality helpful https://en.wikipedia.org/wiki/Virtual_reality#/media/File:Linux_kernel_and_gaming_input-output_latency.svg
A tale about exploiting KernelCTF Mitigation, Debian, and Ubuntu instances with a double-free in nf_tables in the #Linuxkernel, using novel techniques like Dirty Pagedirectory. All without even having to recompile the exploit for different #kernel targets once.
When #Linux#kernel developers file bugs in bugzilla.kernel.org against subsystems that do not use the bug tracker[1]: it seems even they are not aware that the bug most likely won't be forwarded to the responsible developers and thus not be acted upon.
[1] reminder, only a very small fraction of the #LinuxKernel's subsystems use it; how many exactly is hard to say, but only 20 out of 2500+ entries in the MAINTAINERS file point to it.
Go and take a look – and let me know if you spot any mistakes or something else that could be improved!
And thx again to everyone (especially @ptesarik and @corbet) who helped getting this reviewed and merged into the #LinuxKernel's documentation: much appreciated!
"'"This merge window looks to be fairly normal. […]
In contrast, what is meaningful is a couple of very core updates. The timer subsystem had a fairly big rewrite [1][…] The other fairly notable core update is to the workqueue subsystem [2][…]
The core updates should be entirely invisible to users, […]
🔐 Linux 6.9 Adds New RISC-V Vector-Accelerated Crypto Routines - Phoronix
「 RISC-V with Linux 6.9 implements support for more vector-accelerated crypto routines. Among the work is RISC-V vector accelerated AES-{ECB,CBC,CTR,XTS}, ChaCha20, GHASH, SHA-256, SHA-384, SHA-512, SM3, and SM4 algorithms 」
Habe eine #NVMe#SSD in meinem Notebook.
Hin und wieder schafft es das #Linux scheinbar nicht, die SSD korrekt in den Standby zu fahren.
Dann wird sie sehr warm (ca. 50 Grad) und saugt meinen Akku über Nacht leer.
Kennt das Problem jemand?
Google sagt Firmware Update, die ist aber bereits up-to-date.
Was tun?
"[…] The other day I was implementing multi-threaded stat() calls in bfs. When I ran some benchmarks, I saw something that made my heart skip a beat: […]
I searched Google for that "corrupted node" message and found that it had happened to someone else recently too: Linus Torvalds, just after merging a #Btrfs pull request. (This was not the first time Linus and I had hit the same bug. We both have the same CPU in our desktops. […]"