Rust for Linux List
 help / color / mirror / Atom feed
From: FUJITA Tomonori <tomo@flapping.org>
To: a.hindborg@kernel.org
Cc: tomo@flapping.org, ojeda@kernel.org, acourbot@nvidia.com,
	aliceryhl@google.com, anna-maria@linutronix.de,
	bjorn3_gh@protonmail.com, boqun@kernel.org, dakr@kernel.org,
	daniel.almeida@collabora.com, frederic@kernel.org,
	gary@garyguo.net, jstultz@google.com, lossin@kernel.org,
	lyude@redhat.com, sboyd@kernel.org, tamird@kernel.org,
	tglx@kernel.org, tmgross@umich.edu, work@onurozkan.dev,
	rust-for-linux@vger.kernel.org, fujita.tomonori@gmail.com
Subject: Re: [PATCH v4 2/2] rust: hrtimer: Make HrTimer repr(transparent)
Date: Mon, 10 Aug 2026 20:42:48 +0900 (JST)	[thread overview]
Message-ID: <20260810.204248.1426065758894654964.tomo@flapping.org> (raw)
In-Reply-To: <87jypy2pzr.fsf@kernel.org>

On Mon, 10 Aug 2026 13:07:20 +0200
Andreas Hindborg <a.hindborg@kernel.org> wrote:

> "FUJITA Tomonori" <tomo@flapping.org> writes:
> 
>> From: FUJITA Tomonori <fujita.tomonori@gmail.com>
>>
>> HrTimerCallbackContext acquires a &HrTimer<T> from a
>> NonNull<HrTimer<T>> while a &mut HrTimer<T> can exist at the same
>> time. This is sound only because HrTimer's sole field is
>> Opaque<bindings::hrtimer>, which puts every byte behind an UnsafeCell.
>> Adding a field to HrTimer that is not Opaque would make acquiring that
>> shared reference unsound.
>>
>> Make HrTimer repr(transparent), which prevents multiple fields, so that
>> such a refactor fails to compile instead of silently introducing
>> unsoundness. This does not guarantee the remaining field stays behind
>> Opaque, but it rules out the likely way of getting there.
>>
>> repr(transparent) cannot be combined with repr(C), so drop the latter.
>>
>> Suggested-by: Miguel Ojeda <ojeda@kernel.org>
>> Signed-off-by: FUJITA Tomonori <fujita.tomonori@gmail.com>
>> ---
>>  rust/kernel/time/hrtimer.rs         | 6 +++++-
>>  rust/kernel/time/hrtimer/arc.rs     | 2 +-
>>  rust/kernel/time/hrtimer/pin.rs     | 2 +-
>>  rust/kernel/time/hrtimer/pin_mut.rs | 2 +-
>>  rust/kernel/time/hrtimer/tbox.rs    | 2 +-
>>  5 files changed, 9 insertions(+), 5 deletions(-)
>>
>> diff --git a/rust/kernel/time/hrtimer.rs b/rust/kernel/time/hrtimer.rs
>> index 1db84cd4cbe8..04f47af3541b 100644
>> --- a/rust/kernel/time/hrtimer.rs
>> +++ b/rust/kernel/time/hrtimer.rs
>> @@ -418,8 +418,12 @@
>>  /// # Invariants
>>  ///
>>  /// * `self.timer` is initialized by `bindings::hrtimer_setup`.
>> +// `repr(transparent)` is not merely about layout. `HrTimerCallbackContext` acquires a
>> +// `&HrTimer<T>` while a `&mut HrTimer<T>` may exist, which is sound only because every byte of
>> +// this type sits inside `Opaque`. Being transparent rejects a second field at compile time,
>> +// but it does not enforce that the remaining field stays `Opaque`.
> 
> Missing bullet. With that fixed:
> 
> Reviewed-by: Andreas Hindborg <a.hindborg@kernel.org>

This is a plain `//` comment, not documentation. Did you mean that you
want it documented as one of the `# Invariants` bullets instead?


  reply	other threads:[~2026-08-10 11:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gaVV23pVoQuUbm5qsnhQShsVZfOivBkIjMB8yfwrQCi7DeMizBafFVFI0bol4_aolii89peid2LdkWIBA9nMig==@protonmail.internalid>
2026-08-07 23:30 ` [PATCH v4 1/2] rust: hrtimer: Restrict expires() to safe contexts FUJITA Tomonori
2026-08-07 23:30   ` [PATCH v4 2/2] rust: hrtimer: Make HrTimer repr(transparent) FUJITA Tomonori
2026-08-10 11:07     ` Andreas Hindborg
2026-08-10 11:42       ` FUJITA Tomonori [this message]
2026-08-10 13:28         ` Andreas Hindborg
2026-08-10 14:01           ` FUJITA Tomonori
2026-08-10 14:48             ` Andreas Hindborg
2026-08-10 11:11   ` [PATCH v4 1/2] rust: hrtimer: Restrict expires() to safe contexts Andreas Hindborg

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=20260810.204248.1426065758894654964.tomo@flapping.org \
    --to=tomo@flapping.org \
    --cc=a.hindborg@kernel.org \
    --cc=acourbot@nvidia.com \
    --cc=aliceryhl@google.com \
    --cc=anna-maria@linutronix.de \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun@kernel.org \
    --cc=dakr@kernel.org \
    --cc=daniel.almeida@collabora.com \
    --cc=frederic@kernel.org \
    --cc=fujita.tomonori@gmail.com \
    --cc=gary@garyguo.net \
    --cc=jstultz@google.com \
    --cc=lossin@kernel.org \
    --cc=lyude@redhat.com \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=sboyd@kernel.org \
    --cc=tamird@kernel.org \
    --cc=tglx@kernel.org \
    --cc=tmgross@umich.edu \
    --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