mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: gary@garyguo.net
To: Alice Ryhl <aliceryhl@google.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Carlos Llamas" <cmllamas@google.com>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Boqun Feng" <boqun@kernel.org>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <lossin@kernel.org>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Trevor Gross" <tmgross@umich.edu>,
	"Danilo Krummrich" <dakr@kernel.org>,
	linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
	"Matthew Maurer" <mmaurer@google.com>
Subject: Re: [PATCH] rust_binder: avoid name mangling for get_work[_local]
Date: Fri, 13 Feb 2026 23:51:48 +0000	[thread overview]
Message-ID: <fed9bf3d5d9681e1003536be6cd99088@garyguo.net> (raw)
In-Reply-To: <20260213-rust-binder-ps-v1-1-6b90f83c0b4d@google.com>

(Sorry Alice, resending as I didn't hit "Reply All". I was travelling 
and not on my usual email setup).

On 2026-02-13 11:37, Alice Ryhl wrote:
> Currently ps -A shows processes waiting on schedule() in functions with
> names such as do_epoll_wait, wait_woken, and the impeccably named
> _RNvMs2_NtCs8QPsHWIn21X_16rust_binder_main6threadNtB5_6Thread8get_work.
> 
> To improve how ps output looks, give explicit non-mangled names to the
> functions where Rust Binder calls schedule(), since these are the most
> likely places to show up on ps output.
> 
> The name of rust_binder_waitlcl is truncated instead of using _local
> suffix because rust_binder_wait_local is sufficiently long that ps 
> shows
> unaligned output.
> 
> Suggested-by: Matthew Maurer <mmaurer@google.com>
> Signed-off-by: Alice Ryhl <aliceryhl@google.com>

I don't think this the direction that we should head for. It's not 
feasible to
do this for all users that can possibly call `schedule()`. In edition 
2024
forwards, `export_name` is also an unsafe attribute and it will become 
tedious to
justify all usages.

I think if the function names are demangled, it won't be too bad?

Best,
Gary


> ---
>  drivers/android/binder/process.rs | 1 +
>  drivers/android/binder/thread.rs  | 2 ++
>  2 files changed, 3 insertions(+)
> 
> diff --git a/drivers/android/binder/process.rs 
> b/drivers/android/binder/process.rs
> index 
> 132055b4790f0ec69a87635b498909df2bf475e2..cf7425e74183966063ab53114637aec7b3672ac8 
> 100644
> --- a/drivers/android/binder/process.rs
> +++ b/drivers/android/binder/process.rs
> @@ -1436,6 +1436,7 @@ pub(crate) fn drop_outstanding_txn(&self) {
>          }
>      }
> 
> +    #[export_name = "rust_binder_freeze"]
>      pub(crate) fn ioctl_freeze(&self, info: &BinderFreezeInfo) -> 
> Result {
>          if info.enable == 0 {
>              let msgs = self.prepare_freeze_messages()?;
> diff --git a/drivers/android/binder/thread.rs 
> b/drivers/android/binder/thread.rs
> index 
> 1f1709a6a77abc1c865cc9387e7ba7493448c71d..2ca8ed8962314b58a3cfeb3ae0aa0ed60f179433 
> 100644
> --- a/drivers/android/binder/thread.rs
> +++ b/drivers/android/binder/thread.rs
> @@ -514,6 +514,7 @@ pub(crate) fn has_current_transaction(&self) -> 
> bool {
>      /// Attempts to fetch a work item from the thread-local queue. The 
> behaviour if the queue is
>      /// empty depends on `wait`: if it is true, the function waits for 
> some work to be queued (or a
>      /// signal); otherwise it returns indicating that none is 
> available.
> +    #[export_name = "rust_binder_waitlcl"]
>      fn get_work_local(self: &Arc<Self>, wait: bool) -> 
> Result<Option<DLArc<dyn DeliverToRead>>> {
>          {
>              let mut inner = self.inner.lock();
> @@ -552,6 +553,7 @@ fn get_work_local(self: &Arc<Self>, wait: bool) -> 
> Result<Option<DLArc<dyn Deliv
>      ///
>      /// This must only be called when the thread is not participating 
> in a transaction chain. If it
>      /// is, the local version (`get_work_local`) should be used 
> instead.
> +    #[export_name = "rust_binder_wait"]
>      fn get_work(self: &Arc<Self>, wait: bool) -> 
> Result<Option<DLArc<dyn DeliverToRead>>> {
>          // Try to get work from the thread's work queue, using only a 
> local lock.
>          {
> 
> ---
> base-commit: cee73b1e840c154f64ace682cb477c1ae2e29cc4
> change-id: 20260213-rust-binder-ps-46d9d060243a
> 
> Best regards,

  reply	other threads:[~2026-02-13 23:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-13 11:37 Alice Ryhl
2026-02-13 23:51 ` gary [this message]
2026-02-14  0:20   ` Alice Ryhl
2026-02-14  1:54     ` Miguel Ojeda

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=fed9bf3d5d9681e1003536be6cd99088@garyguo.net \
    --to=gary@garyguo.net \
    --cc=a.hindborg@kernel.org \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun@kernel.org \
    --cc=cmllamas@google.com \
    --cc=dakr@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=mmaurer@google.com \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tmgross@umich.edu \
    /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

all inboxes | Powered by JetHome®