[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72n1eo4AX2mHdWkYUmLSy2WOHCGG+X6ZTmtPft7JC+t2jA@mail.gmail.com>
Date: Thu, 3 Nov 2022 10:37:33 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Dennis Dai <dzy.0424thu@...il.com>
Cc: Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org,
Wedson Almeida Filho <wedsonaf@...il.com>,
Andreas Hindborg <andreas@...aspace.dk>
Subject: Re: rust nvme driver: potential sleep-in-atomic-context
On Thu, Nov 3, 2022 at 7:12 AM Dennis Dai <dzy.0424thu@...il.com> wrote:
>
> The rust nvme driver [1] (which is still pending to be merged into
> mainline [2]) has a potential sleep-in-atomic-context bug.
>
> dev.queues.lock().io.try_reserve(nr_io_queues as _)?;
Cc'ing Andreas and fixing Wedson's email. Note that this was written
when it wasn't decided how the `try_*` methods would know about the
flags.
Cheers,
Miguel
Powered by blists - more mailing lists