Rust in Linux kernel, now out of experimental phase.
#kernel
Rust in the Linux kernel is here to stay!
To celebrate this event, we sat down with Danilo Krummrich, Linux kernel maintainer and Rust for Linux core team member about the new NOVA driver and how Rust makes hardware-abstractions safer.
We talk about the typestate pattern, custom allocators, pin-init for self-referential structures, and why code that compiles in Rust actually works instead of causing kernel panics.
Just learned there's a whole middle ground between a dynamic kernel and full RT. All this time I thought it was binary: either “YOLO scheduling” or “monk‑level determinism”. Turns out Linux ships with a surprise third option. The more you know… and the more you recompile.
Booting Linux in QEMU and Writing PID 1 in Go to Illustrate Kernel as Program
https://serversfor.dev/linux-inside-out/the-linux-kernel-is-just-a-program/
#HackerNews #Booting #Linux #QEMU #Go #Kernel #Programming #PID1
Is there anyone who does #linux #Kernel #readings 🤔 I want to know the future of the linux kernel xD hahahaha #satirical question xD
"Rust Goes Mainstream in the Linux Kernel" by @TheNewStack / @sjvn - #Rust🦀 in the #Linux🐧 #Kernel is no longer considered experimental. The programming language made for enforcing memory safety was approved at a kernel developers conference as permanent, alongside the C language it was originally written in. https://thenewstack.io/rust-goes-mainstream-in-the-linux-kernel/ #RustLang #OpenSource #software #engineering #tech
Linux 6.18 ya es oficial y será LTS: lo que tenés que saber #software_y_hardware #descargar_kernel #dm_pcache #kernel_6.18_lts #kernel.org #linux_6.18 #novedades_kernel #rust_kernel #sheaves
https://notilinux.com/linux-6-18-lts-novedades/
Iterating HMAC encryption steadily to be great again: https://lore.kernel.org/linux-integrity/20251210172027.109938-1-jarkko@kernel.org/
I don't think it has unsolvable issues but it will need some rework. Just needs a few iterations like this.
I think also that once it is functionally and quality wise significantly improved it makes sense to replace CONFIG_TCG_TPM_HMAC with kernel command-line parameters and set of parameters.
Other remarks that I put mostly here for myself as a remainder (I love Mastodon bookmarks):
1. One thing that was properly handled in the first iteration was also that despite ECC-NIST-P256/SHA256 might be de-facto and pratically everywhere in western countries, there's also large population in a distant country at Asia relyingon SM2/SM3. I.e. we eventually need SM2/SM3 to be univeral.
2. Initialization itself should be *conditional* i.e., it will complain if feature cannot be enabled but that's all. It can be then supplemented with "panic_on_warn" style parametr, if somone has a problem with this.
3. Relying only on null key generated at boot is a great for some systems (laptops/desktops) but for embedded systems especially it is a major performance hit. Thus also persistent root key should be an option.
4. During power on hwrng was the worst glitch. The patch set above already improves the situation by making read request "opportunistic" instead of committing to an amount. No grand plan for this but I do have a sack of ideas in my pocket. This will gradually improve over time with no grand plan tbh ;-)
#linux #kernel #tpm
I don't think it has unsolvable issues but it will need some rework. Just needs a few iterations like this.
I think also that once it is functionally and quality wise significantly improved it makes sense to replace CONFIG_TCG_TPM_HMAC with kernel command-line parameters and set of parameters.
Other remarks that I put mostly here for myself as a remainder (I love Mastodon bookmarks):
1. One thing that was properly handled in the first iteration was also that despite ECC-NIST-P256/SHA256 might be de-facto and pratically everywhere in western countries, there's also large population in a distant country at Asia relyingon SM2/SM3. I.e. we eventually need SM2/SM3 to be univeral.
2. Initialization itself should be *conditional* i.e., it will complain if feature cannot be enabled but that's all. It can be then supplemented with "panic_on_warn" style parametr, if somone has a problem with this.
3. Relying only on null key generated at boot is a great for some systems (laptops/desktops) but for embedded systems especially it is a major performance hit. Thus also persistent root key should be an option.
4. During power on hwrng was the worst glitch. The patch set above already improves the situation by making read request "opportunistic" instead of committing to an amount. No grand plan for this but I do have a sack of ideas in my pocket. This will gradually improve over time with no grand plan tbh ;-)
#linux #kernel #tpm
Rust in the Linux kernel is officially here to stay - (lwn.net)
Installed new RX 9070XT OC Tiachi GPU on ubuntu 25.10. GPU is not recognized #kernel #gpu #gpudriver
VirtualBox 7.1.14: VirtualBox can't operate in VMX root mode. Please disable the KVM kernel extension #kernel #virtualbox #virtualization
Rust is officially here to stay in the Linux Kernel
https://lwn.net/Articles/1049831/
#RustLang #Linux #Kernel
https://lwn.net/Articles/1049831/
#RustLang #Linux #Kernel
Oh, not only is the connection or sshd killed, the kernel panics and the server reboots:
Dec 10 12:23:36 arthur savecore[1666]: reboot after panic: Solaris(panic): zfs: rt={spa=zroot vdev_guid=1996288907895677832 ms_id=73 ms_freeing}: adding segment (offset=12407e7000 size=1000) overlapping with existing one (offset=1240
Dec 10 12:23:36 arthur savecore[1666]: writing core to /var/crash/vmcore.6
https://forums.freebsd.org/threads/kernel-panic-with-zfs-destroy-on-snapshot.100660/
»Linux-Kernel — Rust-Support offiziell abgesegnet:
Rust wird Assembler und C bei der Programmierung des Linux-Kernels ebenbürtig – zumindest offiziell, denn praktisch gibt es noch viel zu tun.«
Ich pers. sehe das als sehr positiev, da mMn weniger Fehler im Linux Kernel aufkommen können. Klar liegt dies am Coden doch Rust vermindert overflow & Co. und doch/deshalb gibt es viel zu tun.
🐧 https://www.heise.de/news/Linux-Kernel-Rust-Support-offiziell-abgesegnet-11109733.html
#linux #rust #rustlang #coding #kernel #linuxkernel #opensource #CCode #code
kernel.org tooling update from @monsieuricon
https://lore.kernel.org/all/20251209-roaring-hidden-alligator-068eea@lemur/
""These are the topics that were touched on at the [#Linux #kernel] maintainer summit […]
# What is the state of tooling?
## b4 development update
[…]
- Seeing lots of adoption and use across subsystem,
[…]
I spent a lot of time on trying to integrate AI into b4 workflows, but with little to show for it in the end due to lackluster results.
[…]
it was certainly ironic that one of the top challenges for us was to try to keep AI crawlers from overwhelming kernel.org infrastructure.
[…]
## Are we finally moving away from patches sent over email?
[…]
With lore and public-inbox, we *are* in the process of moving away from
relying on the increasingly unreliable SMTP layer.
[…]
## Work on "local lore"
[…]
## Other tools
### Bugzilla
It may be time to kill bugzilla:
[…]""
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst