5 releases

0.2.4 Sep 30, 2024
0.2.3 Mar 26, 2024
0.2.0 Feb 24, 2024
0.1.2 Feb 15, 2024
0.1.0 Jan 27, 2024

#249 in Unix APIs

Download history 5/week @ 2024-09-18 162/week @ 2024-09-25 56/week @ 2024-10-02 23/week @ 2024-10-09 9/week @ 2024-10-16 21/week @ 2024-10-30 226/week @ 2024-11-06 53/week @ 2024-11-13 19/week @ 2024-11-20

314 downloads per month
Used in 2 crates

Apache-2.0

375KB
9K SLoC

rsbinder

rsbinder provides crates implemented in pure Rust that make Binder IPC available on both Android and Linux.

Rust

Binder IPC: Available on Linux, Untapped Potential

While Android's Binder IPC mechanism was merged into the Linux kernel back in 2015, its adoption within the broader Linux ecosystem remains limited. This project aims to address that by providing libraries and tools specifically designed for using Binder IPC in Linux environments.

One key reason for limited adoption is the lack of readily available tools and libraries optimized for the Linux world. This project tackles that challenge by leveraging Rust's strengths for efficient thread utilization, a crucial aspect for maximizing Binder IPC performance on Linux.

However, this project focuses on pure Rust implementations. If you're interested in C++-based Binder IPC for Linux, consider checking out the binder-linux project.

Although this project focuses on supporting Binder IPC in the Linux environment, it also provides compatibility with Android's Binder IPC. Compatibility Goal with Android Binder

Current Development Status

rsbinder is still in its early development stages and is not yet ready for product development.

Overview

rsbinder offers the following features:

Prerequisites to build and test

Enable binder for Linux

  • The Linux kernel must be built with support for binderfs. Please check the following kernel configs.
CONFIG_ASHMEM=y
CONFIG_ANDROID=y
CONFIG_ANDROID_BINDER_IPC=y
CONFIG_ANDROID_BINDERFS=y
  • Arch Linux - Install linux-zen kernel. Zen kernel already includes BinderFS.
$ pacman -S linux-zen

Build rsbinder

Build all rsbinder crates.

$ cargo build

Run rsbinder tools

  • Run rsb_device command to create a binder device file.
$ sudo target/debug/rsb_device binder
  • Run rsb_hub. It is a binder service manager.
$ cargo run --bin rsb_hub

Test binder for Linux

  • Run hello_service
$ cargo run --bin hello_service
  • Run hello_client
$ cargo run --bin hello_client

Cross compile to Android device

Compatibility Goal with Android Binder

Mutual Communication:

Both rsbinder and Android Binder utilize the same core protocol, enabling seamless communication between Android services and rsbinder clients, and vice versa. However, continued development is currently underway to further refine this interoperability.

API Differences:

Complete API parity between rsbinder and Android Binder isn't available due to fundamental differences in their underlying architectures. Nonetheless, both APIs share a high degree of similarity, minimizing the learning curve for developers familiar with either system.

Todo

  • Implement Binder crate.
  • Implement AIDL compiler.
  • Implement ParcelFileDescriptor.
  • Port Android test_service and test_client and pass the test cases.
  • Support Tokio async.
  • (In Progress) Implement Service Manager(rsb_hub) for Linux
  • (In Progress) Remove all todo!() and unimplemented!() macros.
  • (In Progress) Performed compatibility testing with Binder on Android.
  • Enhance error detection in AIDL code generator
  • Support Mandatory Access Control likes selinux and AppArmor.
  • Support AIDL version and hash.

License

rsbinder is licensed under the Apache License version 2.0.

Notice

Many of the source codes in rsbinder have been developed by quoting or referencing Android's binder implementation.

Dependencies

~4–11MB
~124K SLoC