From: Danilo Krummrich <dakr@kernel.org>
To: stable@vger.kernel.org
Cc: gregkh@linuxfoundation.org, aliceryhl@google.com,
lossin@kernel.org, sashal@kernel.org,
Danilo Krummrich <dakr@kernel.org>
Subject: [PATCH 0/4] Devres fixes for v6.15.4
Date: Tue, 24 Jun 2025 15:58:31 +0200 [thread overview]
Message-ID: <20250624135856.60250-1-dakr@kernel.org> (raw)
As discussed in [1], here's the patch series for the Rust Devres fixes for
v6.15.4.
[1] https://lore.kernel.org/stable/2025062455-rogue-flagship-54a4@gregkh/
Danilo Krummrich (4):
rust: completion: implement initial abstraction
rust: revocable: indicate whether `data` has been revoked already
rust: devres: fix race in Devres::drop()
rust: devres: do not dereference to the internal Revocable
rust/bindings/bindings_helper.h | 1 +
rust/helpers/completion.c | 8 +++
rust/helpers/helpers.c | 1 +
rust/kernel/devres.rs | 53 ++++++++++-----
rust/kernel/revocable.rs | 18 +++--
rust/kernel/sync.rs | 2 +
rust/kernel/sync/completion.rs | 112 ++++++++++++++++++++++++++++++++
7 files changed, 175 insertions(+), 20 deletions(-)
create mode 100644 rust/helpers/completion.c
create mode 100644 rust/kernel/sync/completion.rs
base-commit: a2b47f77e740a21dbdcb12e2f2ca3c840299545a
--
2.49.0
next reply other threads:[~2025-06-24 13:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 13:58 Danilo Krummrich [this message]
2025-06-24 13:58 ` [PATCH 1/4] rust: completion: implement initial abstraction Danilo Krummrich
2025-06-25 14:07 ` Sasha Levin
2025-06-24 13:58 ` [PATCH 2/4] rust: revocable: indicate whether `data` has been revoked already Danilo Krummrich
2025-06-25 14:09 ` Sasha Levin
2025-06-24 13:58 ` [PATCH 3/4] rust: devres: fix race in Devres::drop() Danilo Krummrich
2025-06-25 14:08 ` Sasha Levin
2025-06-24 13:58 ` [PATCH 4/4] rust: devres: do not dereference to the internal Revocable Danilo Krummrich
2025-06-25 14:09 ` Sasha Levin
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=20250624135856.60250-1-dakr@kernel.org \
--to=dakr@kernel.org \
--cc=aliceryhl@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=lossin@kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.