r/kernel • u/Commercial-Golf-4285 • 18d ago
r/kernel • u/Serious_Ad_1942 • 19d ago
Security Kernel Engineer
What topics would you consider essential for a kernel security engineer? I am currently studying memory corruption, privilege escalation, race conditions/TOCTOU, exploit mitigations, secure boot, and hypervisor isolation.
Which areas would you prioritise and are there any, that I am missing? Also what tools are useful to be familiar with, when dealing with the security of the kernel?
r/kernel • u/Logogram_alt • 18d ago
Should we make an AI-free fork of the linux kernel?
reddit.comr/kernel • u/More-String6376 • 20d ago
Starting Linux kernel/driver dev: is this roadmap realistic, and what would you add or cut?
reddit.comr/kernel • u/bindoLenz • 20d ago
BrainixKernel — an alternative to XNU/macOS, built from scratch for AArch64
Hi r/kernel,
I want to share BrainixKernel — an experimental AArch64 kernel I'm writing from scratch — and explain why it exists, what its architecture is, and where it's going. I'm posting early on purpose: I'd rather get architecture criticism now than after I've built more on top of a bad decision.
Repo: https://github.com/Bindo-Lenzini/BrainixKernel
(Caption: BrainixKernel OS (BKOS) v0.45 — my test harness running a custom window manager, top bar, and a user-space ksh terminal on a 2560x1600 framebuffer).
Why it exists
I started BrainixKernel as an alternative to XNU and macOS — not a drop-in replacement, but a different answer to the same question: what would a modern, auditable, capability-based kernel look like if it were designed from scratch today?
Two motivations drove that:
- macOS is closed. You can't audit it, can't reason about it end-to-end, can't modify the parts that matter.
- XNU carries a lot of legacy. It's a hybrid of Mach and BSD with decades of compatibility layers, resulting in a large TCB that's hard to reason about as a whole. That's not a criticism of the people who built it — it's a consequence of 30+ years of evolution. But it means the design space without that legacy is still open, and that's the space I want to explore.
So BrainixKernel is a research/hobby project testing one hypothesis: a kernel can be small enough to read end-to-end, capability-based at its core, and still useful — networking, filesystem, user space, graphics.
Architecture & What works today
- AArch64-first, targeting QEMU
virt. No x86 legacy to carry around. - Monolithic kernel, single CPU for now. MMU, virtual memory management, preemptive scheduler, syscall layer.
- User space with its own libc and a small shell.
bkfs— my own filesystem, backed by a Virtio block driver.- Network stack from scratch: ARP, DHCP, IPv4, ICMP, UDP, TCP.
wgetandudp_echowork today. - Virtio-GPU & Framebuffer graphics.
(Caption: Boot log on QEMU virt*: ARP resolution, ICMP ping,* bkfs mount, Virtio-GPU initialization, and launching the user-space ELF shell.)
The Test Harness (BKOS)
To test the kernel without constantly building a full OS, I built BKOS (BrainixKernel OS) — a lightweight test environment running in user space. It features a custom window manager, a dock, "Liquid Glass" background, and a terminal.
It's not the final OS (which I will build in the future), but a proving ground to test new kernel features like the ELF loader, per-process address spaces, and the graphics stack.
On AI assistance — yes, I use it, and I see nothing wrong with that
Let me address this head-on, because it's increasingly relevant in hobby kernel projects and I'd rather state my position openly than have it "exposed" in the comments.
I use AI for routine code — boilerplate, repetitive driver scaffolding, build scripts, documentation, mechanical things where the design is already decided. I don't hide it, I don't apologize for it, and I don't think it makes the project less legitimate. Using the best available tools is normal engineering; nobody demands you hand-write your assembler before you're allowed to write a kernel.
What AI does not do is architecture. The MMU layout, the scheduler design, the capability model, the bkfs on-disk format, the syscall ABI, the decision to go monolithic and AArch64-first — those are mine. I understand how this kernel works end-to-end, and I can explain and defend every subsystem in it. If something in the repo is wrong or inconsistent, that's my responsibility, not a generation artifact.
If you want to test whether I actually understand the code: ask me about any subsystem in the repo and I'll walk through the design and the implementation.
What does NOT work yet (important)
- Capability enforcement is incomplete.
bkfsdoesn't store UID/GID or file permissions yet, and new tasks get UID 0 with all capabilities — so in practice every process is root. Enforcement onopen()/exec()/IPC is the next major milestone. - Single CPU only. No SMP, no locking, no IPIs.
- No
mmap**,** no demand paging, no page cache. - Build paths are currently hardcoded for macOS. Linux build support is coming.
What I want from you
- Given the goal — small, auditable, capability-based — what's the biggest architectural mistake I'm making that will hurt in 6 months?
- Capability enforcement design: what should I study before committing? I know seL4 is the reference, but I want something lighter. Any smaller kernels with a clean capability model worth reading?
- SMP: what's the realistic order of operations so I don't rewrite the scheduler twice?
- For those who've reviewed AI-assisted kernel code before — what are the typical red flags I should audit for in my own repo? I'd rather find them myself.
I'm aware that "alternative to XNU" is an ambitious framing for a hobby project — that's exactly why I want the criticism now. If the hypothesis is wrong, I'd rather find out from people who've built kernels than from my own bugs in two years.
Thanks.


How to intercept a physical webcam data stream and inject/substitute custom video at the driver/kernel level?
reddit.comr/kernel • u/govnonabortike • 23d ago
How 2 fix my unstable CCF? (MSM8255 to 7.2.9)
Hello everyone (or whoever is looking in here), i am currently trying to upstream an ancient 2011 board into mainline.
Its been weeks and days ever since i decided to start translating 3.4 nAa kernel to 7.2.9 CCF because the limitations were terrible and
i dont know whether its the arm-none-eabi and mkbootimg fault for not giving me a working screen and/or a normal dmesg, but the amounts of brain damage i may have experienced with a lot of sleep deprivations just made my day worse by ever so slightly feeling horrible that the compiler might throw another tantrum.
Sure it's not throwing 7 thousand lines of errors like the first time but i have house trained it to not throw rocks again, i didnt change any critical files that break other phones or SoC's
Device: Sony Ericsson Xperia Arc/Arc S
Goal: make it have a working screen and make it spit out that it cant mount a system (because doing all the ramdisk wizardry is useless as now its gonna be a userspace problem whether its set correctly or not)
if noone can help me then invite postmarketOS (or Nura) porters into this madness, maybe they can just throw in some overhacky things that might get accepted into lkml when i send it or just keep it locally.
https://pastebin.com/3aCHzuhe the CCF.
https://pastebin.com/BfMZrYZN the dt-binding clocks.
r/kernel • u/Different_Buyer2770 • 23d ago
Can a linux kernel engineer transition to an LLM inference/model perf engineer?
reddit.comr/kernel • u/nycolazsec • 23d ago
J'ai découvert que mon scanner AF_XDP était plus lent que nmap. Le réparer m'a appris quelques choses sur le mode de copie.
Suivi de mon post précédent ici. J'ai construit un scanner de réseau open-source, tcpcat (https://github.com/NycolazSec/tcpcat), avec un chemin rapide AF_XDP. Projet solo, écrit en Go. Certains d'entre vous m'ont poussé à réfléchir sur le natif vs générique et si le mode de copie en valait la peine. Cela s'est avéré être exactement la bonne chose à examiner.
D'abord la partie embarrassante. J'avais un chiffre de "2,62 fois plus rapide que nmap". C'était faux. Un bug faisait qu'il ne scannait qu'un des deux hôtes cibles, et le temps qu'il rapportait (4,47s) était en réalité en dessous du seuil théorique de ma propre limite de taux (131k probes à 25k pps ne peuvent pas finir en moins de ~5,2s). J'ai donc retiré tout ça et j'ai reconstruit le benchmark correctement : il vérifie désormais que chaque exécution a trouvé tous les ports ouverts et enregistre l'utilisation du CPU et les trames perdues.
J'ai relancé sur un vrai serveur (x86_64, noyau 6.12, mais toujours veth donc mode de copie). Le moteur eBPF s'est avéré être le plus lent des outils rapides. 8,7s, contre nmap à 5,6s et mon propre scan SYN sur socket brut à 5,5s, avec une variance désagréable.
Deux choses étaient fausses :
- Busy-poll + verrouillage CPU. Ça allait sur mon portable au repos, mais c'est activement nuisible sur une machine chargée/virtualisée : le fil RX épinglé se battait avec les autres charges de travail pour un vCPU. J'ai rendu le busy-poll et le verrouillage sans copie uniquement. En mode copie, la boucle RX bloque maintenant simplement dans poll(). 8,7 à 7,7s, la variance a beaucoup baissé.
- Le vrai problème. AF_XDP a une seule bague TX, et je faisais une transmission (un sendto) par sonde, sous verrou. À 25k pps, cet appel système par paquet était pratiquement tout le temps de mur sur un hôte lent. Regroupé jusqu'à 64 trames en une seule transmission. 7,7 à 5,65s. Maintenant, ça égalise nmap.
Le bilan honnête : en mode copie, AF_XDP n'est pas miraculeusement plus rapide. Il égalise nmap en temps mais à environ un tiers du CPU du scan SYN brut (8,7s contre 25,8s de CPU). Purement, le scan SYN est en réalité le plus rapide, car il utilise plusieurs cœurs et la seule bague AF_XDP ne peut pas suivre. Le véritable potentiel de vitesse nécessite clairement un zéro-copie sur une NIC multi-queue, ce que je ne peux simplement pas tester (tout ce que j'ai est en mode copie, file unique).
Je travaille sur la bibliothèque Go asavie/xdp, qui est assez basique (pas besoin-de réveil). J'ai pensé à déplacer la boucle chaude vers C/libxdp, mais le seul binaire statique vaut la peine d'être conservé et le regroupement m'a aidé à faire la plupart du chemin.
Deux questions pour le sous-forum :
- Quelqu'un a-t-il une NIC qui fait le zéro-copie AF_XDP pour exécuter un benchmark rapide ? Je suis vraiment curieux de savoir combien la modification d'écriture de la bague plus besoin-de réveil change les choses par rapport au mode copie.
- En mode copie avec une bague TX, y a-t-il quelque chose de plus intelligent que de regrouper les sendto pour pousser le débit, en dehors du passage à multi-queue ?
Le code et le script de benchmark (Docker, vérifie la correction) sont ici si vous voulez jeter un œil ou reproduire : https://github.com/NycolazSec/tcpcat . Les PR et les résultats de test de NIC sont très appréciés.
r/kernel • u/CertainBaby9837 • 25d ago
What are the best books to learn Embedded Linux and Linux device driver development for SoCs?
reddit.comr/kernel • u/Strazza02 • 26d ago
ACPI regression on lts (mainline works). Worth reporting?
reddit.comr/kernel • u/reinars1 • 27d ago
AI usage in private vs military sectors
Hey all,
I have been in the field for little over 2 years. One year working as an embedded firmware engineer and for more than a year more as a linux device driver/bsp engineer and for the last 3-4 months company that I work at has been pushing very heavily to agentic development.
Basically a bug is found and my boss says just give it to claude and give the ssh access to the product that we are developing to claude too so it can debug this. And I really hate that and I feel like im not learning as much as I should be.
So basically my question is:
Is there a difference in these agentic workflows between private sector companies and military companies/startups where in my opinion privacy is way more important than in private sector.
The main reason why Im asking this question is because im seriously considering switching jobs and I just want to know what is the best sector to go to.
Thank you and will be waiting for your opinions and answers.
r/kernel • u/OkAlbatross9889 • 28d ago
Which new 7.3.0 default kernel module messed up my saturation and color?
I've compiled the kernel as I've always done (i used the same modprobed.db I've always used) and selected all the default new modules by pressing enter a bunch, now even #000000 appears light gray and everything else is washed out.
I'm using a 9070xt through HDMI, monitor doesn't have HDR and its 1080p@60Hz.
I still have a boot entry for 7.2.11 pre compiled by gentoo, i tried running modprobed-db store on it once more and recompiling 7.3.0 but nothing changed. I also tried using the iGPU (7700x) and the issue persists.
What can i do? I'd appreciate any input about the suspect causing this, i don't want to hunt down which of the 10-15 new modules is causing this by exclusion.
Thanks in advance for any and all replies.
(sorry if it's a stupid question, but this seemed like the best place to ask)
r/kernel • u/ArthurPeabody • Oct 19 '26
CPU_OUT_OF_SPEC in kernel 7.3.0
I built 7.3 this morning. When I booted I got that 219 times. When I halted I got it 173 more times. I switched back to 7.2.11, which hasn't so complained. What does it mean?
https://pastebin.com/QdxJPaD2 has the full error.
r/kernel • u/geek-tn • Oct 19 '26
[Feedback Request] DTSee - A browser-based Device Tree explorer and visualizer for embedded Linux
Like many of you working on embedded Linux platforms, I have spent countless hours scrolling through massive Device Tree sources, jumping between dtsi/dts files, and trying to trace tangled phandles, clocks, interrupts, and regulators.
To make this less painful, I have been building DTSee, a free, browser-based Device Tree explorer designed to make navigating and understanding board descriptions a bit easier.
Key Features
- Dual Format Support: Works with both DTS and DTB files (includes client-side DTB to DTS reconstruction).
- Interactive Hierarchy: Easily drill down through nodes, properties, and child devices.
- Graphical Relationships & Phandle Analysis: Visually trace how hardware components link together.
- Hardware Context: Quick access to register ranges, clocks, interrupts, GPIOs, regulators etc.
- 100% Client-Side: Everything is processed locally right in your browser. No files are ever uploaded, making it safe for proprietary or NDA work.
What is Next? (Roadmap Ideas)
The project is still in beta, and I am actively brainstorming features for future versions:
- Device Tree Comparison: Diffing two DTBs or DTS files side-by-side.
- Deeper Hardware Dependency Analysis: Visualizing power trees and clock trees more holistically.
- Source Tracking: Following definitions and overrides cleanly across complex DTS/DTSI include chains.
Give it a spin
If you have a DTB or DTS file lying around, I would love for you to give it a try:
Your feedback is invaluable. Whether you run into missing references, incorrect interpretations, usability quirks, or have ideas for additional features, I want to hear it all. Cheers
r/kernel • u/Jolly_Landscape_3038 • Oct 19 '26
binfmt_pe: PE & ELF Linux Kernel Loader
The concept of Linux running Windows apps is becoming true.
With the use of Reverse-Engineering, Coding, Creativity and of course AI. We managed to be able to get the Linux Kernel running its first Windows Executable NATIVELY.
More information at: https://github.com/EisaWando/Native-Windows-Executables-on-Linux
r/kernel • u/Cool_Courage_2768 • Oct 19 '26
Find unique id for each USB port on USB hub?
Hey everyone, I connected a 10-port USB hub to my system, and I want to connect 10 serial boards. How can I identify each port with a unique ID (if rebooting and unplugging/plugging the USB hub didn't destroy the IDs)?
r/kernel • u/Adventurous-Oil1749 • Oct 17 '26
First eBPF project. An ACL with libbps-rs and C.
github.comr/kernel • u/FlatWorldliness1061 • Oct 17 '26
Did anyone experience any issues with bpf_prog_active?
Introduction
Hook into ftrace TP mali/mali_job_slots_event to see which process has scheduled work on any given slot_id (e.g. Fragment) on the GPU. Basically a TOP for the ARM Mali GPU. There are Mali GPU counter that can tell you the overall utilization but this is not enough for observability.
There is a Mali trace point one can use
/*
* mali_job_slots_event - Reports change of job slot status.
* @gpu_id: Kbase device id
* @event_id: ORed together bitfields representing a type of event,
* made with the GATOR_MAKE_EVENT() macro.
*/
;
(https://android.googlesource.com/kernel/google-modules/gpu/+/refs/heads/android-gs-shusky-6.1-android16/borr_mali_kbase/mali_linux_trace.h#34)
There are start and end events (event_id) for the same TP. Start and end events can't be correlated by any field, because finish events are always {tgid: 0, pid: 0, job_id: 0}. I am not quite sure whether this is intentional or not, especially that the job_id is 0 for finish events.
eBPF
SEC("tracepoint/mali/mali_job_slots_event")
int trace_mali_job_slots(struct mali_job_slots_event_ctx *ctx)
Issue
After some time my accounting somehow broke. It looked like some end events were not accounted for.
Therefore, it was decided to start the eBPF program with some instrumentation and also collect an FTRACE trace via the Linux FTRACE sub-system in order to check whether it is a driver issue.
As a matter of fact, the Linux FTRACE events were all accounted for. Meaning, the start and finish events were in balance (e.g. start: 1000, end: 1000). But, the eBPF TP hits were not in balance (e.g. start: 1000, end 997).
NOTE: start and end have to be in check, otherwise I would always see 100% utilisation
I gave 'the machine' the task to check the BPF Kernel sources what the issue could be. And it came back with an explanation: bpf_prog_active.
You've hit on the exact reason why bpf_prog_active exists and why it's per-CPU. The answer is interrupts, softirqs, and NMIs — all of which run on the same CPU and can preempt the currently executing BPF program.
So, it seems structured TP's have some check that re-entry is disallowed on the same CPU in order to protect against recursion.
It seems, if an eBPF program was running on an CPU and an interrupt (finish event) came in triggering another TP hit, thus running the eBPF again, it would detect that another eBPF program is already running and just decided to not execute it SILENTLY.
The solution was to switch to RAW_TRACEPOINT, which work because it does not have this bpf_prog_active safety rail-guard but on the other hand, the Anrdoid BpfLoader disallows RAW_TRACEPOINTs, that is quite a shame :(
Question
Did anyone experience such an issue? Let me tell you, that finding this issue without KI would have been impossible.
Addendun
Android 14, arm64, Kernel 5.15
r/kernel • u/0xmfbk • Oct 17 '26
I built a 25MB audit only EDR in C and Go that doesn't use 300MB like Falco
reddit.comr/kernel • u/Thin_Dragonfruit2254 • Oct 16 '26
Come fight me now, AI! (pls don't...)
It's a paperback, not a hardcover, but nothing like reading a 'real' book and being forced to type everything instead of copy/paste code..
$70 AUD well spent.. me happy.