[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <172373175849.6989.2668092199011403509.b4-ty@kernel.dk>
Date: Thu, 15 Aug 2024 08:22:38 -0600
From: Jens Axboe <axboe@...nel.dk>
To: Miguel Ojeda <ojeda@...nel.org>, Alex Gaynor <alex.gaynor@...il.com>,
Wedson Almeida Filho <wedsonaf@...il.com>,
Andreas Hindborg <nmi@...aspace.dk>
Cc: Andreas Hindborg <a.hindborg@...sung.com>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <benno.lossin@...ton.me>, Alice Ryhl <aliceryhl@...gle.com>,
"Behme Dirk (XC-CP/ESB5)" <Dirk.Behme@...bosch.com>,
linux-block@...r.kernel.org, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] rust: fix erranous use of lock class key in rust
block device bindings
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
Powered by blists - more mailing lists