From: Alice Ryhl <aliceryhl@google.com>
To: Pieter-Louis Schoeman <pl.schoeman@pocketlaw.net>
Cc: arve@android.com, brauner@kernel.org, cmllamas@google.com,
gregkh@linuxfoundation.org, tkjos@android.com,
linux-kernel@vger.kernel.org, ojeda@kernel.org,
paul@paul-moore.com, tamird@gmail.com, vitaly.wool@konsulko.se,
wedsonaf@gmail.com, yury.norov@gmail.com
Subject: Re: [PATCH] binder: rust: pin zero-to-one ref increments to initiating thread
Date: Wed, 17 Dec 2025 20:43:00 +0000 [thread overview]
Message-ID: <aUMV1Kv8dtHLVWIc@google.com> (raw)
In-Reply-To: <20251215194541.19425-1-pl.schoeman@pocketlaw.net>
On Mon, Dec 15, 2025 at 09:45:41PM +0200, Pieter-Louis Schoeman wrote:
> The refcount update path must use the zero-to-one aware API on the first
> increment to preserve correct delivery semantics.
>
> Pass the initiating thread through Process::update_ref() and NodeRef so
> zero->one increments are pinned when available, while keeping decrement
> behavior unchanged.
>
> Also harden update_refcount_locked() to reject increments.
>
> Signed-off-by: Pieter-Louis Schoeman <pl.schoeman@pocketlaw.net>
Currently the zero-to-one aware API is used only when a process sends an
outgoing transaction containing a node owned by the sender. Can you
explain what other scenario requires the zero-to-one aware API?
Alice
prev parent reply other threads:[~2025-12-17 20:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 19:45 [PATCH] binder: rust: pin zero-to-one ref increments to initiating thread Pieter-Louis Schoeman
2025-12-17 20:43 ` Alice Ryhl [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=aUMV1Kv8dtHLVWIc@google.com \
--to=aliceryhl@google.com \
--cc=arve@android.com \
--cc=brauner@kernel.org \
--cc=cmllamas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=paul@paul-moore.com \
--cc=pl.schoeman@pocketlaw.net \
--cc=tamird@gmail.com \
--cc=tkjos@android.com \
--cc=vitaly.wool@konsulko.se \
--cc=wedsonaf@gmail.com \
--cc=yury.norov@gmail.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