linux-kernel - Re: [PATCH] rust_binder: add Rust Binder driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <aMw7SmMz8CXOelix@google.com>
Date: Thu, 18 Sep 2025 17:03:06 +0000
From: Carlos Llamas <cmllamas@...gle.com>
To: Alice Ryhl <aliceryhl@...gle.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Arve Hjønnevåg <arve@...roid.com>,
	Todd Kjos <tkjos@...roid.com>, Martijn Coenen <maco@...roid.com>,
	Joel Fernandes <joelagnelf@...dia.com>,
	Christian Brauner <brauner@...nel.org>,
	Suren Baghdasaryan <surenb@...gle.com>,
	Miguel Ojeda <ojeda@...nel.org>, Boqun Feng <boqun.feng@...il.com>,
	Gary Guo <gary@...yguo.net>,
	Björn Roy Baron <bjorn3_gh@...tonmail.com>,
	Benno Lossin <lossin@...nel.org>,
	Andreas Hindborg <a.hindborg@...nel.org>,
	Trevor Gross <tmgross@...ch.edu>,
	Danilo Krummrich <dakr@...nel.org>,
	Lorenzo Stoakes <lorenzo.stoakes@...cle.com>,
	"Liam R. Howlett" <Liam.Howlett@...cle.com>,
	Paul Moore <paul@...l-moore.com>, Serge Hallyn <sergeh@...nel.org>,
	linux-kernel@...r.kernel.org, rust-for-linux@...r.kernel.org,
	Wedson Almeida Filho <wedsonaf@...il.com>,
	Matt Gilbride <mattgilbride@...gle.com>
Subject: Re: [PATCH] rust_binder: add Rust Binder driver

On Thu, Sep 18, 2025 at 04:55:11PM +0000, Alice Ryhl wrote:
> On Thu, Sep 18, 2025 at 04:19:57PM +0000, Carlos Llamas wrote:
> > Hmm, is there anyway to keep a single binderfs.c implementation? In this
> > case we now have separate CONFIGs we could use for the file creation
> > callback? It would be nice to keep a single binderfs source file.
> 
> It could be nice, but it's pretty non-trivial to unify them. If we do
> that, it will have to be a follow-up, and the follow-up will modify C
> Binder too.
> 

Ok, that is fine then. I can look more into this part once it lands.

Feel free to add to you next version:

Acked-by: Carlos Llamas <cmllamas@...gle.com>