From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Carlos Llamas <cmllamas@google.com>
Cc: "Arve Hjønnevåg" <arve@android.com>,
"Todd Kjos" <tkjos@android.com>,
"Christian Brauner" <brauner@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Shuah Khan" <shuah@kernel.org>,
kernel-team@android.com, linux-kernel@vger.kernel.org,
rust-for-linux@vger.kernel.org,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH] binder: rm -f binder.c
Date: Sun, 13 Sep 2026 08:02:17 +0200 [thread overview]
Message-ID: <2026091341-engulf-tattoo-ca3b@gregkh> (raw)
In-Reply-To: <rm-c-binder@google.com>
On Sat, Sep 12, 2026 at 09:41:10PM +0000, Carlos Llamas wrote:
> The day has finally come. We are dropping the legacy C implementation
> of the Binder IPC driver in favor of its Rust version.
>
> For 15+ years, the C driver has grown increasingly complex, making it
> incredibly painful to maintain and land new features without tripping
> over vulnerabilities. The Rust implementation alleviates most of
> these issues, so it's time for a change.
>
> Alice Ryhl has worked hard on the Rust binder for the past couple of
> years, not only achieving full feature parity but also proving that it
> can match and often beat the performance of the C counterpart. Having
> run successfully on Android devices for some time now, we can no longer
> call this an "experiment".
>
> It's time to move on, yank the C code, and focus all new features and
> optimizations on the Rust driver.
>
> Long live the new Rust Binder king!
>
> Cc: rust-for-linux@vger.kernel.org
> Acked-by: Alice Ryhl <aliceryhl@google.com>
> Signed-off-by: Carlos Llamas <cmllamas@google.com>
> ---
> drivers/android/Kconfig | 39 +-
> drivers/android/Makefile | 5 +-
> drivers/android/binder.c | 7186 -----------------
> drivers/android/binder/Makefile | 4 +-
> drivers/android/binder/rust_binder_main.rs | 2 +-
> drivers/android/binder/rust_binderfs.c | 2 +-
> drivers/android/binder_alloc.c | 1409 ----
> drivers/android/binder_alloc.h | 189 -
> drivers/android/binder_internal.h | 597 --
> drivers/android/binder_netlink.c | 32 -
> drivers/android/binder_netlink.h | 21 -
> drivers/android/binder_trace.h | 448 -
> drivers/android/binderfs.c | 786 --
> drivers/android/dbitmap.h | 169 -
> drivers/android/tests/.kunitconfig | 7 -
> drivers/android/tests/Makefile | 6 -
> drivers/android/tests/binder_alloc_kunit.c | 572 --
> rust/bindings/bindings_helper.h | 2 +-
> .../filesystems/binderfs/binderfs_test.c | 2 +-
> .../selftests/filesystems/binderfs/config | 1 -
> 20 files changed, 9 insertions(+), 11470 deletions(-)
Yeah!!!
Great job everyone on this, I'll queue this up this week when I catch up
on pending binder fixes/patches...
thanks,
greg k-h
prev parent reply other threads:[~2026-09-13 6:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 21:41 [PATCH] binder: rm -f binder.c Carlos Llamas
2026-09-13 6:02 ` Greg Kroah-Hartman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026091341-engulf-tattoo-ca3b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=aliceryhl@google.com \
--cc=arve@android.com \
--cc=brauner@kernel.org \
--cc=cmllamas@google.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=tkjos@android.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox