linux-kernel - Re: [PATCH v3 3/3] rust_binder: handle PID namespace conversion for freeze operation

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] [day] [month] [year] [list]

Message-ID: <aYRS4K035jOL1fXv@google.com>
Date: Thu, 5 Feb 2026 08:20:48 +0000
From: Alice Ryhl <aliceryhl@...gle.com>
To: jongan.kim@....com
Cc: a.hindborg@...nel.org, arve@...roid.com, bjorn3_gh@...tonmail.com, 
	boqun.feng@...il.com, brauner@...nel.org, cmllamas@...gle.com, 
	dakr@...nel.org, daniel.almeida@...labora.com, gary@...yguo.net, 
	gregkh@...uxfoundation.org, heesu0025.kim@....com, ht.hong@....com, 
	jungsu.hwang@....com, kernel-team@...roid.com, linux-kernel@...r.kernel.org, 
	lossin@...nel.org, ojeda@...nel.org, rust-for-linux@...r.kernel.org, 
	sanghun.lee@....com, seulgi.lee@....com, sunghoon.kim@....com, 
	tamird@...il.com, tkjos@...roid.com, tmgross@...ch.edu, 
	viresh.kumar@...aro.org, vitaly.wool@...sulko.se, yury.norov@...il.com
Subject: Re: [PATCH v3 3/3] rust_binder: handle PID namespace conversion for
 freeze operation

On Thu, Feb 05, 2026 at 02:01:28PM +0900, jongan.kim@....com wrote:
> On Wed, Feb 04 2026 10:50:31AM +0000, Alice Ryhl wrote:
> > On Wed, Feb 04, 2026 at 06:11:47PM +0900, jongan.kim@....com wrote:
> > > 3. Regarding the search mechanism and vec efficiency improvements you
> > > mentioned, these seem like valuable optimizations but would represent
> > > a broader architectural change to the binder driver.
> > 
> > Improving get_procs_with_pid() seems like a separate thing. Perhaps it
> > could be part of this other series:
> > https://lore.kernel.org/all/20260201000817.275382-1-shivamklr@cock.li/
> > 
> > Improving it here should only happen if you need to rewrite said
> > function *anyway*.
> 
> Since we're changing the implementation to use task-based comparison instead
> of PID-based comparison, we won't be using get_procs_with_pid() anymore and
> will need to write a new function (e.g., get_procs_with_task()).
> 
> Would this approach align with the Rust binder development direction?

Replacing get_procs_with_pid() with a new get_procs_with_task() sounds
reasonable to me.

Alice