From: Jens Axboe <axboe@kernel.dk>
To: Miguel Ojeda <ojeda@kernel.org>,
Alex Gaynor <alex.gaynor@gmail.com>,
Wedson Almeida Filho <wedsonaf@gmail.com>,
Andreas Hindborg <nmi@metaspace.dk>
Cc: "Andreas Hindborg" <a.hindborg@samsung.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Alice Ryhl" <aliceryhl@google.com>,
"Behme Dirk (XC-CP/ESB5)" <Dirk.Behme@de.bosch.com>,
linux-block@vger.kernel.org, rust-for-linux@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] rust: fix erranous use of lock class key in rust block device bindings
Date: Thu, 15 Aug 2024 08:22:38 -0600 [thread overview]
Message-ID: <172373175849.6989.2668092199011403509.b4-ty@kernel.dk> (raw)
In-Reply-To: <20240815074519.2684107-1-nmi@metaspace.dk>
On Thu, 15 Aug 2024 07:49:37 +0000, Andreas Hindborg wrote:
> The rust block device bindings include a wrong use of lock class key. This
> causes a WARN trace when lockdep is enabled and a `GenDisk` is constructed.
>
> This series fixes the issue by using a static lock class key. To do this, the
> series first fixes the rust build system to correctly export rust statics from
> the bss segment.
>
> [...]
Applied, thanks!
[2/2] rust: block: fix wrong usage of lockdep API
commit: d28b514ea3ae15274a4d70422ecc873bf6258e77
Best regards,
--
Jens Axboe
next prev parent reply other threads:[~2024-08-15 14:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 7:49 Andreas Hindborg
2024-08-15 7:49 ` [PATCH 2/2] rust: block: fix wrong usage of lockdep API Andreas Hindborg
2024-08-15 8:04 ` Alice Ryhl
2024-08-15 19:05 ` Benno Lossin
2024-08-15 19:15 ` Benno Lossin
2024-08-15 21:34 ` Boqun Feng
2024-08-15 19:07 ` Gary Guo
2024-08-15 21:32 ` Boqun Feng
2024-08-15 21:42 ` Gary Guo
2024-08-16 13:08 ` Benno Lossin
2024-08-15 10:02 ` Dirk Behme
2024-08-16 15:59 ` Benno Lossin
2024-08-15 14:22 ` Jens Axboe [this message]
2024-08-15 15:31 ` [PATCH 0/2] rust: fix erranous use of lock class key in rust block device bindings Miguel Ojeda
2024-08-15 16:00 ` Jens Axboe
2024-08-16 8:54 ` Miguel Ojeda
2024-08-21 10:50 ` Miguel Ojeda
2024-08-21 11:36 ` Miguel Ojeda
2024-08-21 11:54 ` Miguel Ojeda
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=172373175849.6989.2668092199011403509.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=Dirk.Behme@de.bosch.com \
--cc=a.hindborg@samsung.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nmi@metaspace.dk \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=wedsonaf@gmail.com \
/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®