From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-lf1-f50.google.com (mail-lf1-f50.google.com [209.85.167.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 664E630EF69 for ; Sun, 18 Jan 2026 10:35:53 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.167.50 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768732557; cv=none; b=ovIoYRRQ9WihPqgeNId5IgJ2xR7P2cboTVLqQfSgKqdQ/0HtDBoQGlp8WI6jMSomiaOJZ2uU2Z6iPLMIufKEUF42MKzR+AWJ9Wy03O3EraGrH7OX83kbgsq7Vs2vZvzdDpP1VK0rpf3GOE09jmtCXzu5OZk3FPNfsxtKS+H75q8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768732557; c=relaxed/simple; bh=likXx3lsQApM6JONVukVE/Mpr53YqrYKc4J3h53njsY=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=s6L+FT/KuW9lILhf61awQ4aBw9NWmK0Mrdt0QsV78yYEFPSDS/lSM6hn+R6pGQJK+res+lHFbnL44skYMb4wvJSfCgTFP58nZvnMP0k+iebeioSTd3u89x+jPZb2cH3i69fe7Ab7QLhPzKDJ5APRTCwES56qsXKnAkEVEC0NT+E= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b=kBC3r4Ow; arc=none smtp.client-ip=209.85.167.50 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="kBC3r4Ow" Received: by mail-lf1-f50.google.com with SMTP id 2adb3069b0e04-59b6a987346so3076783e87.3 for ; Sun, 18 Jan 2026 02:35:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1768732551; x=1769337351; darn=vger.kernel.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=do81nvqxnQsd+JF7gNbhz4jmsUyXkHo3tqbXNTfxmZ8=; b=kBC3r4OwQpQGSFCLD6i/wzML339xRAlEep3ziADim9nWLSwpJPlBYTVZvbEe/fzfBu cU3QgVeAxtsgKngwq233TZ4KwGzZ3p62RUhubqeyz6K1FObm2sO0ZtGTf+BwTdg7rHZ+ 46YDlglU0ng5TNRFaUttuBGEVxRBZ4YrhM/upx0gMqiaBW4gQXUTKIqqReYJshlrDqKP PS+1BSgPcmtT+RonfPPdCDCctQZD/a9a2ud9X/uzbZgEogS5nqJRVmp3viA2ELVblKnI X2kC4ttC/OjSI/12+KVHFB6f1YuFzUvCLJ0b/yDlaF28aJTmIv0GRVJjPlkzWwkUC33L l8QQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1768732551; x=1769337351; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=do81nvqxnQsd+JF7gNbhz4jmsUyXkHo3tqbXNTfxmZ8=; b=Oe952gIrg0CA6wIMwBi1sHzXWHPaIrOZVh+CZUlnrh7/fdLSDjYr9v1zgUG2C2YYq0 zczAoUHivk7TNu60yeDaa739XHuDoUdYzI0n26nZ07zG8it0NHHM4Uc57BxUDRhnfqkm 1jtrGD1VhDHorQGR1xe+iOxsLM5AeHzEmCYlr/+BtOHHIjCKgAjI+VmTlt9LcpC4g4+K ohXN6t0KMhS0mc/1O0zYdNnJDqAZ5sckuMEa7m67mxE6yMr1pd6z+wpmQmNDEQccBSQO mi1CL+UAciRH2fDbTTKuax7Hq9cRdrCqIuCytBWhTx81oUUioTYhcQ+1Oe419sLqnaKn 4RJg== X-Forwarded-Encrypted: i=1; AJvYcCW6tHF1S5JEct0MnhCn78QwCwL7VfqpGuOVZO2DxQrGP1CCyb2W3De5I/LUWf2R7v2mElDD48UgiF1E/QU=@vger.kernel.org X-Gm-Message-State: AOJu0Yyk3cZjH1bCC9aj3JBUeH8dZSoYQNQtyvFV+5LPUL0jr6tuuGBQ xOZz3eyXYXaOpOKtYcmy0kVPQobf76+hx5XcXxlj0BIK4EnAZUhzYrBS X-Gm-Gg: AY/fxX60jaIT7r5+qhrus5kjo0MYKcavR2nyMXEkrd2W7HYgcGBsaXESc27iv3OTdoe kqolpOHmz0xujQhVfHK9voyqPkxqE+x6mawRQjlwT8MTE96hNfiJrE2o5qhcyOqn0imm7kBWDw1 4HWxpGeF33NHV+7AJGQ9swGTQ0rGz92+NPLRT/BpjVw1vJI+Dftox/+GRSEAFEH3YrXQnd0F91M cSdzrN0PGx9qPdwTPwOVUqQNWlL05WI9RLv+5iwqBGjevTqvQxaQVQE5d0r+fncJVsXQzZiJbzt x2bwOH4Go1CK9Dq7xpaiOPeY+3u4+hI4V63zsJcIzhYhaamwYoduz1NpWqtAWtnJ/PCqUdvTfaM /VSOT//uPkkGE23tzLr9/I90+KlpZHALCMeRLquP3RiD42Jyw21XrNuPiaZ1mQmxRGhCDx7q/pI cVedm2eX7twjOnw1s29uP/m+Pa5kSAMkIAjQgrC9hBayOT0KiI71GhbPjpykqrNaGudVeXITaFr uzDRw3f1oScce0ue3KBMrWeI3FM8CmEGcug4i8XJuiaZx8ROnEJsnSQ X-Received: by 2002:a05:6402:5114:b0:64b:93f4:bf85 with SMTP id 4fb4d7f45d1cf-654b955ce0dmr6185816a12.10.1768725520910; Sun, 18 Jan 2026 00:38:40 -0800 (PST) Received: from ?IPV6:2003:df:bf2d:e300:8193:226f:9765:711d? (p200300dfbf2de3008193226f9765711d.dip0.t-ipconnect.de. [2003:df:bf2d:e300:8193:226f:9765:711d]) by smtp.gmail.com with ESMTPSA id 4fb4d7f45d1cf-654533cc5d6sm7155488a12.22.2026.01.18.00.38.37 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 18 Jan 2026 00:38:39 -0800 (PST) Message-ID: <67e5482b-93ed-4b5f-8375-f7e68c50a436@gmail.com> Date: Sun, 18 Jan 2026 09:38:36 +0100 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH 4/5] rust: sync: atomic: Add Atomic<*mut T> support To: Boqun Feng , rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org, rcu@vger.kernel.org Cc: Miguel Ojeda , Gary Guo , =?UTF-8?Q?Bj=C3=B6rn_Roy_Baron?= , Benno Lossin , Andreas Hindborg , Alice Ryhl , Trevor Gross , Danilo Krummrich , Will Deacon , Peter Zijlstra , Mark Rutland , "Paul E. McKenney" , Frederic Weisbecker , Neeraj Upadhyay , Joel Fernandes , Josh Triplett , Uladzislau Rezki , Steven Rostedt , Mathieu Desnoyers , Lai Jiangshan , Zqiang , FUJITA Tomonori References: <20260117122243.24404-1-boqun.feng@gmail.com> <20260117122243.24404-5-boqun.feng@gmail.com> Content-Language: de-AT-frami From: Dirk Behme In-Reply-To: <20260117122243.24404-5-boqun.feng@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 17.01.26 13:22, Boqun Feng wrote: > Atomic pointer support is an important piece of synchronization > algorithm, e.g. RCU, hence provide the support for that. > > Note that instead of relying on atomic_long or the implementation of > `Atomic`, a new set of helpers (atomic_ptr_*) is introduced for > atomic pointer specifically, this is because ptr2int casting would > lose the provenance of a pointer and even though in theory there are a > few tricks the provenance can be restored, it'll still be a simpler > implementation if C could provide atomic pointers directly. The side > effects of this approach are: we don't have the arithmetic and logical > operations for pointers yet and the current implementation only works > on ARCH_SUPPORTS_ATOMIC_RMW architectures, but these are implementation > issues and can be added later. > > Signed-off-by: Boqun Feng > --- > rust/helpers/atomic_ext.c | 3 +++ > rust/kernel/sync/atomic.rs | 12 +++++++++++- > rust/kernel/sync/atomic/internal.rs | 21 +++++++++++++++------ > rust/kernel/sync/atomic/predefine.rs | 23 +++++++++++++++++++++++ > 4 files changed, 52 insertions(+), 7 deletions(-) > > diff --git a/rust/helpers/atomic_ext.c b/rust/helpers/atomic_ext.c > index 240218e2e708..c267d5190529 100644 > --- a/rust/helpers/atomic_ext.c > +++ b/rust/helpers/atomic_ext.c > @@ -36,6 +36,7 @@ __rust_helper void rust_helper_atomic_##tname##_set_release(type *ptr, type val) > > GEN_READ_SET_HELPERS(i8, s8) > GEN_READ_SET_HELPERS(i16, s16) > +GEN_READ_SET_HELPERS(ptr, const void *) > > /* > * xchg helpers depend on ARCH_SUPPORTS_ATOMIC_RMW and on the > @@ -59,6 +60,7 @@ rust_helper_atomic_##tname##_xchg##suffix(type *ptr, type new) \ > > GEN_XCHG_HELPERS(i8, s8) > GEN_XCHG_HELPERS(i16, s16) > +GEN_XCHG_HELPERS(ptr, const void *) > > /* > * try_cmpxchg helpers depend on ARCH_SUPPORTS_ATOMIC_RMW and on the > @@ -82,3 +84,4 @@ rust_helper_atomic_##tname##_try_cmpxchg##suffix(type *ptr, type *old, type new) > > GEN_TRY_CMPXCHG_HELPERS(i8, s8) > GEN_TRY_CMPXCHG_HELPERS(i16, s16) > +GEN_TRY_CMPXCHG_HELPERS(ptr, const void *) > diff --git a/rust/kernel/sync/atomic.rs b/rust/kernel/sync/atomic.rs > index 4aebeacb961a..4d2a5228c2e4 100644 > --- a/rust/kernel/sync/atomic.rs > +++ b/rust/kernel/sync/atomic.rs > @@ -51,6 +51,10 @@ > #[repr(transparent)] > pub struct Atomic(AtomicRepr); > > +// SAFETY: `Atomic` is safe to transfer between execution contexts because of the safety > +// requirement of `AtomicType`. > +unsafe impl Send for Atomic {} > + > // SAFETY: `Atomic` is safe to share among execution contexts because all accesses are atomic. > unsafe impl Sync for Atomic {} > > @@ -68,6 +72,11 @@ unsafe impl Sync for Atomic {} > /// > /// - [`Self`] must have the same size and alignment as [`Self::Repr`]. > /// - [`Self`] must be [round-trip transmutable] to [`Self::Repr`]. > +/// - [`Self`] must be safe to transfer between execution contexts, if it's [`Send`], this is > +/// automatically satisfied. The exception is pointer types that are even though marked as > +/// `!Send` (e.g. raw pointers and [`NonNull`]) but requiring `unsafe` to do anything > +/// meaningful on them. This is because transferring pointer values between execution contexts is > +/// safe as long as the actual `unsafe` dereferencing is justified. > /// > /// Note that this is more relaxed than requiring the bi-directional transmutability (i.e. > /// [`transmute()`] is always sound between `U` and `T`) because of the support for atomic > @@ -108,7 +117,8 @@ unsafe impl Sync for Atomic {} > /// [`transmute()`]: core::mem::transmute > /// [round-trip transmutable]: AtomicType#round-trip-transmutability > /// [Examples]: AtomicType#examples > -pub unsafe trait AtomicType: Sized + Send + Copy { > +/// [`NonNull`]: core::ptr::NonNull > +pub unsafe trait AtomicType: Sized + Copy { > /// The backing atomic implementation type. > type Repr: AtomicImpl; > } > diff --git a/rust/kernel/sync/atomic/internal.rs b/rust/kernel/sync/atomic/internal.rs > index 0dac58bca2b3..93f5a7846645 100644 > --- a/rust/kernel/sync/atomic/internal.rs > +++ b/rust/kernel/sync/atomic/internal.rs > @@ -7,6 +7,7 @@ > use crate::bindings; > use crate::macros::paste; > use core::cell::UnsafeCell; > +use ffi::c_void; > > mod private { > /// Sealed trait marker to disable customized impls on atomic implementation traits. > @@ -14,10 +15,11 @@ pub trait Sealed {} > } > > // The C side supports atomic primitives only for `i32` and `i64` (`atomic_t` and `atomic64_t`), > -// while the Rust side also layers provides atomic support for `i8` and `i16` > -// on top of lower-level C primitives. > +// while the Rust side also provides atomic support for `i8`, `i16` and `*const c_void` on top of > +// lower-level C primitives. > impl private::Sealed for i8 {} > impl private::Sealed for i16 {} > +impl private::Sealed for *const c_void {} > impl private::Sealed for i32 {} > impl private::Sealed for i64 {} > > @@ -26,10 +28,10 @@ impl private::Sealed for i64 {} > /// This trait is sealed, and only types that map directly to the C side atomics > /// or can be implemented with lower-level C primitives are allowed to implement this: > /// > -/// - `i8` and `i16` are implemented with lower-level C primitives. > +/// - `i8`, `i16` and `*const c_void` are implemented with lower-level C primitives. > /// - `i32` map to `atomic_t` > /// - `i64` map to `atomic64_t` > -pub trait AtomicImpl: Sized + Send + Copy + private::Sealed { > +pub trait AtomicImpl: Sized + Copy + private::Sealed { > /// The type of the delta in arithmetic or logical operations. > /// > /// For example, in `atomic_add(ptr, v)`, it's the type of `v`. Usually it's the same type of > @@ -51,6 +53,13 @@ impl AtomicImpl for i16 { > type Delta = Self; > } > > +// The current helpers of load/store uses `{WRITE,READ}_ONCE()` hence the atomicity is only uses -> use ? > +// guaranteed against read-modify-write operations if the architecture supports native atomic RmW. > +#[cfg(CONFIG_ARCH_SUPPORTS_ATOMIC_RMW)] > +impl AtomicImpl for *const c_void { > + type Delta = isize; > +} Are all users of this guarded with CONFIG_ARCH_SUPPORTS_ATOMIC_RMW as well? Or do we want (need?) to cover the non-CONFIG_ARCH_SUPPORTS_ATOMIC_RMW cases where someone tries to use this as well? Best regards Dirk