From: Boqun Feng <boqun@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Ingo Molnar" <mingo@kernel.org>, "Will Deacon" <will@kernel.org>,
"Boqun Feng" <boqun@kernel.org>,
"Waiman Long" <longman@redhat.com>, "Gary Guo" <gary@garyguo.net>,
"Alice Ryhl" <aliceryhl@google.com>,
"Lyude Paul" <lyude@redhat.com>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Onur Özkan" <work@onurozkan.dev>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Danilo Krummrich" <dakr@kernel.org>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org
Subject: [RESEND] [GIT PULL] Rust synchronization changes for v7.3 (Part 1)
Date: Wed, 5 Aug 2026 06:06:34 -0700 [thread overview]
Message-ID: <anM1WvFfRYfc-wHV@tardis.local> (raw)
Hi Peter,
(Resend this since it missed the public list Cc)
Since the SpinLockIrq still needs some reviews. Let me send the first
part of Rust synchronization first. I'm not going to resend them as
patches since they were in [1] already. Could you please pull these in
first if they look good to you? Thanks!
The following changes since commit 1c7efabfbaf796f11000a46094a69955a01ec6cc:
futex: Avoid private hash use-after-free on final put (2026-08-04 12:29:45 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/boqun/linux.git tags/rust-sync.20260804a
for you to fetch changes up to 3f90c16d413b2f68407f1c5bb112a1b16ea35dc4:
rust: revocable: Use LKMM atomics instead of Rust atomics (2026-08-04 05:52:54 -0700)
----------------------------------------------------------------
Rust synchronization changes for v7.3 (Part 1)
- Add synchronize_rcu() safe abstraction.
- Generic memory barrier: this extends Rust barrier primitives to
include the DMA barriers.
- Replace the atomic usage in Revocable with LKMM atomic.
[1]: https://lore.kernel.org/rust-for-linux/20260731203031.13679-1-boqun@kernel.org/
Regards,
Boqun
reply other threads:[~2026-08-05 13:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=anM1WvFfRYfc-wHV@tardis.local \
--to=boqun@kernel.org \
--cc=aliceryhl@google.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=lyude@redhat.com \
--cc=mingo@kernel.org \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=will@kernel.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