Search
231 results for “kernellogger”
-
Interesting detail in the description of the main EFI changes merged for #Linux 6.9[1]:
"'"Avoid creating mappings that are both writable and executable while running in the EFI boot services. This is a prerequisite for getting the x86 #shim loader signed by MicroSoft again, which allows the distros to install on x86 PCs that ship with EFI secure boot enabled."'"
[1] https://git.kernel.org/torvalds/c/70ef654469b371d0a71bcf967fa3dcbca05d4b25
-
Interesting detail in the description of the main EFI changes merged for #Linux 6.9[1]:
"'"Avoid creating mappings that are both writable and executable while running in the EFI boot services. This is a prerequisite for getting the x86 #shim loader signed by MicroSoft again, which allows the distros to install on x86 PCs that ship with EFI secure boot enabled."'"
[1] https://git.kernel.org/torvalds/c/70ef654469b371d0a71bcf967fa3dcbca05d4b25
-
Interesting detail in the description of the main EFI changes merged for #Linux 6.9[1]:
"'"Avoid creating mappings that are both writable and executable while running in the EFI boot services. This is a prerequisite for getting the x86 #shim loader signed by MicroSoft again, which allows the distros to install on x86 PCs that ship with EFI secure boot enabled."'"
[1] https://git.kernel.org/torvalds/c/70ef654469b371d0a71bcf967fa3dcbca05d4b25
-
Interesting detail in the description of the main EFI changes merged for #Linux 6.9[1]:
"'"Avoid creating mappings that are both writable and executable while running in the EFI boot services. This is a prerequisite for getting the x86 #shim loader signed by MicroSoft again, which allows the distros to install on x86 PCs that ship with EFI secure boot enabled."'"
[1] https://git.kernel.org/torvalds/c/70ef654469b371d0a71bcf967fa3dcbca05d4b25
-
#Glibc 2.43 is out:
https://inbox.sourceware.org/libc-alpha/13932477.uLZWGnKmhe@pinacolada/
A few highlights:
* Experimental support for building with #clang has been added.
* [a bunch of ISO C23 stuff]
* Support for mseal and openat2 on #Linux
* Additional optimized and correctly rounded mathematical functions have been imported from the CORE-MATH project […]
* Unicode support has been updated to Unicode 17.0.0.
-
""Dumping packets from a network interface is a common debugging step. […] excessive and uncontrolled dumping can quickly become overwhelming, in terms of the amount of data and the impact on the inspected system. […] In this article, we will explore Retis[1] filtering capabilities, highlighting the differences, similarities, and expectations compared to other existing tools.""
https://developers.redhat.com/articles/2025/10/02/filtering-packets-anywhere-networking-stack
[1] from https://github.com/retis-org/retis "Retis – #Tracing (filtered) packets in the #Linux #networking stack, using #eBPF probes and interfacing with control and data paths such as #OvS or #Netfilter."
-
"'[…] #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. […]'"
https://graphite.dev/blog/bitkeeper-linux-story-of-git-creation
-
Introduction to VirtIO, Part 2: Vhost
https://blogs.oracle.com/linux/post/introduction-to-virtio-part-2-vhost
Jonah Palmer writes: ""[…] #Vhost is a key optimization to #VirtIO that was created to offload data-plane processing from #Qemu into more efficient components.
We’ll start off by taking a more in-depth look into the causes of overhead in the data plane of a pure VirtIO configuration. We’ll talk about the costly operations that are involved, such as VM exits, VM entries, context switches, and userspace processing by Qemu. Then we’ll introduce vhost and elaborate on how it addresses these issues by moving data-plane operations either into the kernel (kernel-based vhost) or into a specialized userspace process (via vhost-user).
We’ll then dive into both #kernel-based vhost and vhost-user architectures, examining each in detail—including their advantages, drawbacks, typical use cases, and how they affect performance. […]"
-
From the main #ntfs3 merge for #Linux 6.17[1]:
"Added:
- sanity check for file name
- mark live inode as bad and avoid any operationsFixed:
- handling of symlinks created in windows
- creation of symlinks for relative pathChanged:
- cancel setting inode as bad after removing name fails
- revert 'replace inode_trylock with inode_lock'"[1] https://git.kernel.org/torvalds/c/a11b4fa602ed3b744aa075f34bee82c12aa3553a
-
From the main #ntfs3 merge for #Linux 6.17[1]:
"Added:
- sanity check for file name
- mark live inode as bad and avoid any operationsFixed:
- handling of symlinks created in windows
- creation of symlinks for relative pathChanged:
- cancel setting inode as bad after removing name fails
- revert 'replace inode_trylock with inode_lock'"[1] https://git.kernel.org/torvalds/c/a11b4fa602ed3b744aa075f34bee82c12aa3553a
-
From the main #ntfs3 merge for #Linux 6.17[1]:
"Added:
- sanity check for file name
- mark live inode as bad and avoid any operationsFixed:
- handling of symlinks created in windows
- creation of symlinks for relative pathChanged:
- cancel setting inode as bad after removing name fails
- revert 'replace inode_trylock with inode_lock'"[1] https://git.kernel.org/torvalds/c/a11b4fa602ed3b744aa075f34bee82c12aa3553a
-
From the main #ntfs3 merge for #Linux 6.17[1]:
"Added:
- sanity check for file name
- mark live inode as bad and avoid any operationsFixed:
- handling of symlinks created in windows
- creation of symlinks for relative pathChanged:
- cancel setting inode as bad after removing name fails
- revert 'replace inode_trylock with inode_lock'"[1] https://git.kernel.org/torvalds/c/a11b4fa602ed3b744aa075f34bee82c12aa3553a
-
From the main #ntfs3 merge for #Linux 6.17[1]:
"Added:
- sanity check for file name
- mark live inode as bad and avoid any operationsFixed:
- handling of symlinks created in windows
- creation of symlinks for relative pathChanged:
- cancel setting inode as bad after removing name fails
- revert 'replace inode_trylock with inode_lock'"[1] https://git.kernel.org/torvalds/c/a11b4fa602ed3b744aa075f34bee82c12aa3553a
-
One highlight from the main #NTFS3 updates merged for #Linux #kernel 6.2:
https://git.kernel.org/torvalds/c/6022ec6ee2c3a16b26f218d7abb538afb839bd6d #LinuxKernel- added mount options:
* 'hide_dot_files' (docs: https://git.kernel.org/torvalds/c/60adc860ca7d7a95d5befd2d3c3e644d23706b2c; note, initially the option was named 'hidedotfiles', see https://git.kernel.org/torvalds/c/dc0fcc99b1756c3c703326aa0015ed73fc4e9a73)
* 'nocase' (https://git.kernel.org/torvalds/c/a3a956c78efaa202b1d75190136671cf6e87bfbe)
* 'windows_names' (doc: https://git.kernel.org/torvalds/c/d683c67c5f50802b9b14ea29d89d66a25327e965)
-
One highlight from the main #NTFS3 updates merged for #Linux #kernel 6.2:
https://git.kernel.org/torvalds/c/6022ec6ee2c3a16b26f218d7abb538afb839bd6d #LinuxKernel- added mount options:
* 'hide_dot_files' (docs: https://git.kernel.org/torvalds/c/60adc860ca7d7a95d5befd2d3c3e644d23706b2c; note, initially the option was named 'hidedotfiles', see https://git.kernel.org/torvalds/c/dc0fcc99b1756c3c703326aa0015ed73fc4e9a73)
* 'nocase' (https://git.kernel.org/torvalds/c/a3a956c78efaa202b1d75190136671cf6e87bfbe)
* 'windows_names' (doc: https://git.kernel.org/torvalds/c/d683c67c5f50802b9b14ea29d89d66a25327e965)
-
One highlight from the main #NTFS3 updates merged for #Linux #kernel 6.2:
https://git.kernel.org/torvalds/c/6022ec6ee2c3a16b26f218d7abb538afb839bd6d #LinuxKernel- added mount options:
* 'hide_dot_files' (docs: https://git.kernel.org/torvalds/c/60adc860ca7d7a95d5befd2d3c3e644d23706b2c; note, initially the option was named 'hidedotfiles', see https://git.kernel.org/torvalds/c/dc0fcc99b1756c3c703326aa0015ed73fc4e9a73)
* 'nocase' (https://git.kernel.org/torvalds/c/a3a956c78efaa202b1d75190136671cf6e87bfbe)
* 'windows_names' (doc: https://git.kernel.org/torvalds/c/d683c67c5f50802b9b14ea29d89d66a25327e965)
-
One highlight from the main #NTFS3 updates merged for #Linux #kernel 6.2:
https://git.kernel.org/torvalds/c/6022ec6ee2c3a16b26f218d7abb538afb839bd6d #LinuxKernel- added mount options:
* 'hide_dot_files' (docs: https://git.kernel.org/torvalds/c/60adc860ca7d7a95d5befd2d3c3e644d23706b2c; note, initially the option was named 'hidedotfiles', see https://git.kernel.org/torvalds/c/dc0fcc99b1756c3c703326aa0015ed73fc4e9a73)
* 'nocase' (https://git.kernel.org/torvalds/c/a3a956c78efaa202b1d75190136671cf6e87bfbe)
* 'windows_names' (doc: https://git.kernel.org/torvalds/c/d683c67c5f50802b9b14ea29d89d66a25327e965)
-
One highlight from the main #NTFS3 updates merged for #Linux #kernel 6.2:
https://git.kernel.org/torvalds/c/6022ec6ee2c3a16b26f218d7abb538afb839bd6d #LinuxKernel- added mount options:
* 'hide_dot_files' (docs: https://git.kernel.org/torvalds/c/60adc860ca7d7a95d5befd2d3c3e644d23706b2c; note, initially the option was named 'hidedotfiles', see https://git.kernel.org/torvalds/c/dc0fcc99b1756c3c703326aa0015ed73fc4e9a73)
* 'nocase' (https://git.kernel.org/torvalds/c/a3a956c78efaa202b1d75190136671cf6e87bfbe)
* 'windows_names' (doc: https://git.kernel.org/torvalds/c/d683c67c5f50802b9b14ea29d89d66a25327e965)
-
'"Many #profiling tools on #Linux have previously been limited by their reliance on stack unwinding algorithms that require commonly-used frame pointer optimizations to be disabled. This article introduces eu-stacktrace, a prototype tool that uses the #elfutils toolkit’s unwinding libraries to support a sampling profiler to unwind frame pointer-less stack sample data."'
https://developers.redhat.com/articles/2024/06/11/get-system-wide-profiles-binaries-without-frame-pointers (from Serhei Makarov)
-
The Input Stack on Linux – An End-To-End Architecture Overview
https://venam.net/blog/unix/2025/11/27/input_devices_linux.html
Patrick Louis writes: ""Let’s explore and deobfuscate the input stack on #Linux. Our aim is to understand its components and what each does. Input handling can be divided into two parts, separated by a common layer:
#Kernel-level handling: It deals with what happens in the kernel and how events are exposed to user-space
[…]
Exposed layer (middle)
[…]
User-space handling:
[…]
The Widgets, #XServer, #X11 window managers, and #Wayland compositors, which rely on everything elseWe’ll try to make sense of all this, one thing at a time, with a logical and coherent approach.""
-
Really wondering what "upstream" actually refers to in "built-in #Debian #Linux environment with upstream support"
* Qualcomm?
* Debian? [Edit: stable or testing?]
* Upstream #LinuxKernel, #Mesa, et. al.?
Screenshot from https://docs.arduino.cc/hardware/uno-q/
-
'"the Trusted Platform Module (TPM) […] allows an unattended auto-unlock, providing a pass is no longer required. That completely fits to secure disks that have been put in a machine in a safe location. With FDE [Full Disk Encryption] and TPM, your data becomes protected and cannot be read outside of your machine."'
https://www.suse.com/c/full-disk-encryption-grub2-tpm/ #grub #tpm #FullDiskEncryption
-
"An explanation of how #Linux handles system calls on x86-64 and why they show up as expensive operations in performance profiles
https://blog.codingconfessions.com/p/what-makes-system-calls-expensive – from Abhinav Upadhyay
-
GNU #Binutils 2.44 is out:
https://lists.gnu.org/archive/html/info-gnu/2025-02/msg00001.html
Some highlights:
* Assembler:
- Support for new architecture extensions for AArch64, Risc-V and x86.* Linker:
- This now supports mixed LTO and non-LTO object files in relocatable output.
- The ELF forms of the linker support a --image-base=<ADDR> option for compatibility with LLD.[…] does not contain the sources for the gold linker […] now deprecated and will eventually be removed unless volunteers step forward […]
-
Sebastian Aaltonen writes:
""[…]Modern graphics API have improved gradually in the past 10 years. […] As of today, there’s no single API that meets all our requirements, but if we combine their best bits together, we can build the perfect API for modern hardware.
10 years ago, modern APIs were designed for CPU-driven binding models. New bindless features were presented as optional features and extensions. A clean break would improve the usability and reduce the API bloat and driver complexity significantly. It’s extremely difficult to get the whole industry behind a brand new API. I am hoping that vendors are willing to drop backwards compatibility in their new major API versions (Vulkan 2.0, DirectX 13) to embrace the fully bindless GPU architecture we have today. […]
-
These two @lwn articles are prime examples of why good journalism matters and why you should pay money to make sure it thrives:
They both look beyond the shiny statements from the different parties involved and outside commentators such as @torvalds in this case and explain just how it is from a mostly neutral[1] point of view so that you can make your own judgments.
* GPLv2 and installation requirements – https://lwn.net/Articles/1052842/
* SFC v. VIZIO: who can enforce the GPL? – https://lwn.net/Articles/1052734/
[1] We are humans, and even if we try, we are never completely neutral – and a publication like #LWN that targets the FLOSS community obviously will somewhat look at things from the view of its target audience.
-
#Memtest86+ 7.0.0 is out: https://github.com/memtest86plus/memtest86plus/releases/tag/v7.00
"'"This release adds support for IMC (Integrated Memory Controller) polling to get live RAM settings on Intel Core 1st to 14th Gen and AMD Ryzen CPUs, and preliminary ECC polling support for selected AMD Ryzen CPUs.
Complete changelog:
IMC polling for live DRAM settings
Preliminary support for ECC polling
Add support for MMIO UART
Add debugging options
Bug fixes & optimizations"'" -
""The name sure sounds like “mutex”, and that is where the name comes from: “fast, user space mutex”. But, it isn’t really, it’s a building block for concurrency primitives that ushered in a modern world of concurrent performance […]
t was immediately clear that the futex was a huge improvement in highly concurrent environments. Just in that original paper, their tests with 1000 parallel tasks ran 20-120 times faster than sysv locks..🤯
Needless to say, other common operating systems followed suit, including Windows in 2012 and macOS by 2016.
These days, any good locking primitive is going to be based on a futex. […]""
-
Have you heard the claim "Changing 30 lines of code in the #Linux #kernel could cut energy use at some data centers by up to 30 percent" that made the news two or three weeks ago?
Did you wonder if it is really that simple as it sounds in many stories? Then you want to read the following article from @LWN. It describes things in a more nuanced and technical way, as yes, it is not that simple:
https://lwn.net/Articles/1008399/ #LinuxKernel #networking #powerefficiency
-
And with that, #Itanium aka #IA64/IA-64 support is gone from the #Linux #kernel:
https://git.kernel.org/torvalds/c/1e0c505e13162a2abe7c984309cfe2ae976b428d
https://git.kernel.org/torvalds/c/cf8e8658100d4eae80ce9b21f7a81cb024dd5057 (that's the main removal patch, which is about ~2 MByte big)
Bye bye!