From: Boqun Feng <boqun@kernel.org>
To: FUJITA Tomonori <tomo@flapping.org>
Cc: aliceryhl@google.com, arve@android.com, brauner@kernel.org,
cmllamas@google.com, gary@garyguo.net,
gregkh@linuxfoundation.org, ojeda@kernel.org, tkjos@android.com,
a.hindborg@kernel.org, acourbot@nvidia.com,
bjorn3_gh@protonmail.com, dakr@kernel.org,
daniel.almeida@collabora.com, lossin@kernel.org,
lyude@redhat.com, tamird@kernel.org, tmgross@umich.edu,
work@onurozkan.dev, linux-kernel@vger.kernel.org,
rust-for-linux@vger.kernel.org,
FUJITA Tomonori <fujita.tomonori@gmail.com>
Subject: Re: [PATCH v9] rust: sync: condvar: use Delta<Jiffy> for timeout and result
Date: Mon, 2 Nov 2026 07:51:29 -0800 [thread overview]
Message-ID: <auixgbeSSfBWwVS9@tardis.local> (raw)
In-Reply-To: <20261102035934.711973-1-tomo@flapping.org>
On Mon, Nov 02, 2026 at 12:59:34PM +0900, FUJITA Tomonori wrote:
> From: FUJITA Tomonori <fujita.tomonori@gmail.com>
>
> wait_interruptible_timeout() takes the timeout as a raw Jiffies, and
> CondVarTimeoutResult reports the remaining time as a raw Jiffies. The
> type does not show the unit.
>
> Switch the parameter and the result fields to Delta<Jiffy>.
>
> Delta<Jiffy> is signed, but schedule_timeout() prints an error and a
> stack dump for a negative timeout. Clamp a negative timeout to zero, so
> it means an immediate timeout.
>
> Update the only user, binder. It now converts the freeze timeout with
> Delta::to_jiffies_timeout() instead of msecs_to_jiffies(). Both round
> up, so a short timeout does not become zero. They differ only for a
> very long timeout. msecs_to_jiffies() returns MAX_JIFFY_OFFSET for
> 2^31 ms (about 24.9 days) or more, which means an infinite
> timeout. to_jiffies_timeout() has no such special case. It converts
> such a value to the matching number of jiffies, so the wait is long
> but finite.
>
> Reviewed-by: Gary Guo <gary@garyguo.net>
> Signed-off-by: FUJITA Tomonori <fujita.tomonori@gmail.com>
Thanks. Alice, any concern regarding the change in binder?
I have some naming suggestion, please see below:
> ---
> v9:
> - Send as a single patch. Patches 1/4 and 2/4 of v8 are in v7.4-rc1,
> and the workqueue patch will be sent separately
> - Rebase on v7.4-rc1
> - Drop the comparison with enqueue_delayed() from the commit message
> v8: https://lore.kernel.org/rust-for-linux/20261002050428.2746277-1-tomo@flapping.org/
> ---
> drivers/android/binder/process.rs | 7 ++++---
> rust/kernel/sync/condvar.rs | 31 ++++++++++++++++++++++---------
> 2 files changed, 26 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/android/binder/process.rs b/drivers/android/binder/process.rs
> index 1f4cb43f1de6..edde0ea35687 100644
> --- a/drivers/android/binder/process.rs
> +++ b/drivers/android/binder/process.rs
> @@ -35,6 +35,7 @@
> Arc, ArcBorrow, CondVar, CondVarTimeoutResult, SetOnce, SpinLock, UniqueArc,
> },
> task::{Pid, Task},
> + time::Delta,
> uaccess::{UserSlice, UserSliceReader},
> uapi,
> workqueue::{self, Work},
> @@ -1552,8 +1553,8 @@ pub(crate) fn ioctl_freeze(&self, info: &BinderFreezeInfo) -> Result {
> inner.is_frozen = IsFrozen::InProgress;
>
> if info.timeout_ms > 0 {
> - let mut jiffies = kernel::time::msecs_to_jiffies(info.timeout_ms);
> - while jiffies > 0 {
> + let mut jiffies = Delta::from_millis(info.timeout_ms.into()).to_jiffies_timeout();
I would rename this variable to `timeout`, i.e.
let timeout = Delta::from_millis(info.timeout_ms.into()).to_jiffies_timeout();
Thoughts?
> + while jiffies.as_jiffies() > 0 {
> if inner.outstanding_txns == 0 {
> break;
> }
> @@ -1570,7 +1571,7 @@ pub(crate) fn ioctl_freeze(&self, info: &BinderFreezeInfo) -> Result {
> jiffies = remaining;
> }
> CondVarTimeoutResult::Timeout => {
> - jiffies = 0;
> + jiffies = Delta::ZERO;
> }
> }
> }
> diff --git a/rust/kernel/sync/condvar.rs b/rust/kernel/sync/condvar.rs
> index 69d58dfbad7b..ae70e91eca94 100644
> --- a/rust/kernel/sync/condvar.rs
> +++ b/rust/kernel/sync/condvar.rs
> @@ -12,7 +12,10 @@
> task::{
> MAX_SCHEDULE_TIMEOUT, TASK_FREEZABLE, TASK_INTERRUPTIBLE, TASK_NORMAL, TASK_UNINTERRUPTIBLE,
> },
> - time::Jiffies,
> + time::{
> + Delta,
> + Jiffy, //
> + },
> types::Opaque,
> };
> use core::{marker::PhantomPinned, pin::Pin, ptr};
> @@ -182,19 +185,29 @@ pub fn wait_interruptible_freezable<T: ?Sized, B: Backend>(
> /// Atomically releases the given lock (whose ownership is proven by the guard) and puts the
> /// thread to sleep. It wakes up when notified by [`CondVar::notify_one`] or
> /// [`CondVar::notify_all`], or when a timeout occurs, or when the thread receives a signal.
> + ///
> + /// A negative timeout is treated as zero.
> #[must_use = "wait_interruptible_timeout returns if a signal is pending, so the caller must check the return value"]
> pub fn wait_interruptible_timeout<T: ?Sized, B: Backend>(
> &self,
> guard: &mut Guard<'_, T, B>,
> - jiffies: Jiffies,
> + delta: Delta<Jiffy>,
s/delta/timeout as well.
> ) -> CondVarTimeoutResult {
> - let jiffies = jiffies.try_into().unwrap_or(MAX_SCHEDULE_TIMEOUT);
> - let res = self.wait_internal(TASK_INTERRUPTIBLE, guard, jiffies);
> + let jiffies = delta.as_jiffies();
> + let res = self.wait_internal(
> + TASK_INTERRUPTIBLE,
> + guard,
> + jiffies.clamp(0, MAX_SCHEDULE_TIMEOUT),
> + );
>
> - match (res as Jiffies, crate::current!().signal_pending()) {
> - (jiffies, true) => CondVarTimeoutResult::Signal { jiffies },
> + match (res, crate::current!().signal_pending()) {
> + (jiffies, true) => CondVarTimeoutResult::Signal {
s/jiffies/remainder
> + jiffies: Delta::from_jiffies(jiffies),
> + },
> (0, false) => CondVarTimeoutResult::Timeout,
> - (jiffies, false) => CondVarTimeoutResult::Woken { jiffies },
> + (jiffies, false) => CondVarTimeoutResult::Woken {
s/jiffies/remainder
> + jiffies: Delta::from_jiffies(jiffies),
> + },
> }
> }
>
> @@ -248,11 +261,11 @@ pub enum CondVarTimeoutResult {
> /// Somebody woke us up.
> Woken {
> /// Remaining sleep duration.
> - jiffies: Jiffies,
> + jiffies: Delta<Jiffy>,
> },
> /// A signal occurred.
> Signal {
> /// Remaining sleep duration.
> - jiffies: Jiffies,
> + jiffies: Delta<Jiffy>,
Similar for these two: s/jiffies/remainder
Thoughts?
Regards,
Boqun
> },
> }
>
> base-commit: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
> --
> 2.43.0
>
prev parent reply other threads:[~2026-11-02 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 3:59 [PATCH v9] rust: sync: condvar: use Delta<Jiffy> for timeout and result FUJITA Tomonori
2026-11-02 15:51 ` Boqun Feng [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=auixgbeSSfBWwVS9@tardis.local \
--to=boqun@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=arve@android.com \
--cc=bjorn3_gh@protonmail.com \
--cc=brauner@kernel.org \
--cc=cmllamas@google.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=lyude@redhat.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@kernel.org \
--cc=tkjos@android.com \
--cc=tmgross@umich.edu \
--cc=tomo@flapping.org \
--cc=work@onurozkan.dev \
/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