From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, boqun.feng@gmail.com
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.6.y] rust: lockdep: Remove support for dynamically allocated LockClassKeys
Date: Tue, 18 Mar 2025 16:12:41 -0400 [thread overview]
Message-ID: <20250318160404-df5cff5d101acbb2@stable.kernel.org> (raw)
In-Reply-To: <20250318180447.4958-1-boqun.feng@gmail.com>
[ Sasha's backport helper bot ]
Hi,
Summary of potential issues:
⚠️ Found matching upstream commit but patch is missing proper reference to it
Found matching upstream commit: 966944f3711665db13e214fef6d02982c49bb972
WARNING: Author mismatch between patch and found commit:
Backport author: Boqun Feng<boqun.feng@gmail.com>
Commit author: Mitchell Levy<levymitchell0@gmail.com>
Status in newer kernel trees:
6.13.y | Present (different SHA1: 3e5d366aabae)
6.12.y | Present (different SHA1: c5b195dd9564)
Note: The patch differs from the upstream commit:
---
1: 966944f371166 ! 1: b037a70e0eccb rust: lockdep: Remove support for dynamically allocated LockClassKeys
@@ Commit message
Reviewed-by: Benno Lossin <benno.lossin@proton.me>
Cc: stable@vger.kernel.org
Link: https://lore.kernel.org/r/20250307232717.1759087-11-boqun.feng@gmail.com
+ (cherry picked from commit 966944f3711665db13e214fef6d02982c49bb972)
+ Signed-off-by: Boqun Feng <boqun.feng@gmail.com>
## rust/kernel/sync.rs ##
@@
@@ rust/kernel/sync.rs
pub(crate) fn as_ptr(&self) -> *mut bindings::lock_class_key {
self.0.get()
}
- }
-
--impl Default for LockClassKey {
-- fn default() -> Self {
-- Self::new()
-- }
--}
--
- /// Defines a new static lock class and returns a pointer to it.
- #[doc(hidden)]
+@@ rust/kernel/sync.rs: pub(crate) fn as_ptr(&self) -> *mut bindings::lock_class_key {
#[macro_export]
macro_rules! static_lock_class {
() => {{
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.6.y | Success | Success |
prev parent reply other threads:[~2025-03-18 20:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-16 7:15 FAILED: patch "[PATCH] rust: lockdep: Remove support for dynamically allocated" failed to apply to 6.6-stable tree gregkh
2025-03-18 17:59 ` Boqun Feng
2025-03-18 19:59 ` Greg KH
2025-03-18 18:04 ` [PATCH 6.6.y] rust: lockdep: Remove support for dynamically allocated LockClassKeys Boqun Feng
2025-03-18 20:12 ` Sasha Levin [this message]
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=20250318160404-df5cff5d101acbb2@stable.kernel.org \
--to=sashal@kernel.org \
--cc=boqun.feng@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox