From: Alice Ryhl <aliceryhl@google.com>
To: stable@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <sashal@kernel.org>,
Danilo Krummrich <dakr@kernel.org>
Cc: "Alexandre Courbot" <acourbot@nvidia.com>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Benno Lossin" <lossin@kernel.org>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Boris Brezillon" <boris.brezillon@collabora.com>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Eliot Courtney" <ecourtney@nvidia.com>,
"Gary Guo" <gary@garyguo.net>,
"Markus Probst" <markus.probst@posteo.de>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
"Alice Ryhl" <aliceryhl@google.com>,
Sashiko <sashiko-bot@kernel.org>
Subject: [PATCH 6.18.y 0/5] Four Rust Devres fixes
Date: Mon, 05 Oct 2026 09:47:25 +0000 [thread overview]
Message-ID: <20261005-devres-6-18-backport-v1-0-06dcf0e592d5@google.com> (raw)
These fixes were not picked up because of some conflicts and/or build
failures, but they are important to avoid deadlocks and races. Please
pick them up for 6.18, thanks!
Unfortunately, it turns out that backporting these fixes introduces a
bug in the irq abstraction due to the fact that it makes Devres
allocate. This bug is not present in mainline because irq no longer uses
Devres at all upstream. I included a fix for this as well.
Signed-off-by: Alice Ryhl <aliceryhl@google.com>
---
Alice Ryhl (1):
rust: irq: pass RegistrationInner as cookie to request_irq
Danilo Krummrich (4):
rust: devres: fix race condition due to nesting
rust: devres: add 'static bound to Devres<T>
rust: devres: fix race between concurrent revokers
rust: devres: ensure revocation is complete before device finishes unbinding
rust/kernel/devres.rs | 164 ++++++++++++++++++---------------------------
rust/kernel/irq/request.rs | 89 ++++++++++++++----------
2 files changed, 119 insertions(+), 134 deletions(-)
---
base-commit: 1b357ecb321392158d507b04672ffee57bfa071d
change-id: 20260930-devres-6-18-backport-93f976775b42
Best regards,
--
Alice Ryhl <aliceryhl@google.com>
next reply other threads:[~2026-10-05 9:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 9:47 Alice Ryhl [this message]
2026-10-05 9:47 ` [PATCH 6.18.y 1/5] rust: devres: fix race condition due to nesting Alice Ryhl
2026-10-05 9:47 ` [PATCH 6.18.y 2/5] rust: devres: add 'static bound to Devres<T> Alice Ryhl
2026-10-05 9:47 ` [PATCH 6.18.y 3/5] rust: devres: fix race between concurrent revokers Alice Ryhl
2026-10-05 9:47 ` [PATCH 6.18.y 4/5] rust: devres: ensure revocation is complete before device finishes unbinding Alice Ryhl
2026-10-05 9:47 ` [PATCH 6.18.y 5/5] rust: irq: pass RegistrationInner as cookie to request_irq Alice Ryhl
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=20261005-devres-6-18-backport-v1-0-06dcf0e592d5@google.com \
--to=aliceryhl@google.com \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=ecourtney@nvidia.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=markus.probst@posteo.de \
--cc=ojeda@kernel.org \
--cc=rafael@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=sashiko-bot@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tmgross@umich.edu \
/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
all inboxes | Powered by JetHome®