VOOZH about

URL: https://www.phoronix.com/news/BUS1-Linux-2026

⇱ New Rust-Based BUS1 In-Kernel IPC In Development For The Linux Kernel - Phoronix


👁 Phoronix

New Rust-Based BUS1 In-Kernel IPC In Development For The Linux Kernel

Written by Michael Larabel in Linux Kernel on 31 March 2026 at 03:47 PM EDT. 40 Comments
After KDBUS failed to make it into the mainline Linux kernel more than one decade ago as an in-kernel version of D-Bus, BUS1 was proposed as a clean sheet design for in-kernel, capability-based inter-process communication (IPC). BUS1 didn't gain enough traction to make it to the mainline kernel and then many of the same developers devised Dbus-Broker as a more performant D-Bus user-space implementation. Well, as a big surprise now, a new version of BUS1 is being worked on for the Linux kernel.

David Rheinsberg who was one of the original developers working on BUS1 has announced a new version of this IPC system for Linux. The same core ideas from a decade ago are in place while now it also has gone from being C code to Rust.

This new BUS1 version was stripped down to the basics and implemented in the Rust programming language. This initial announcement today went out on the Rust-For-Linux mailing list to gain feedback on the Rust aspect of this BUS1 implementation.

👁 BUS1 logo


The new BUS1 in Rust comes in at 16 patches and just under nine thousand lines of new code, but more work is still to be completed in tackling all of its planned features and functionality.

Those interested in this new BUS1 rewrite in Rust can find the code on the Rust-For-Linux mailing list.

Michael Larabel is the principal author of Phoronix.com and founded the site in 2004 with a focus on enriching the Linux hardware experience. Michael has written more than 20,000 articles covering the state of Linux hardware support, Linux performance, graphics drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated benchmarking software. He can be followed via Twitter, LinkedIn, or contacted via MichaelLarabel.com.