Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <CACMswuMVERF_+R3Qxb0xGHCBQUCuxtBLA+eDo__Coed3BoVC3A@mail.gmail.com>
In-Reply-To: <CACMswuMVERF_+R3Qxb0xGHCBQUCuxtBLA+eDo__Coed3BoVC3A@mail.gmail.com>
From:   Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Date:   Thu, 3 Nov 2022 10:37:33 +0100
Message-ID: <CANiq72n1eo4AX2mHdWkYUmLSy2WOHCGG+X6ZTmtPft7JC+t2jA@mail.gmail.com>
Subject: Re: rust nvme driver: potential sleep-in-atomic-context
To:     Dennis Dai <dzy.0424thu@gmail.com>
Cc:     Miguel Ojeda <ojeda@kernel.org>,
        Alex Gaynor <alex.gaynor@gmail.com>,
        Boqun Feng <boqun.feng@gmail.com>, Gary Guo <gary@garyguo.net>,
        =?UTF-8?Q?Bj=C3=B6rn_Roy_Baron?= <bjorn3_gh@protonmail.com>,
        rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
        Wedson Almeida Filho <wedsonaf@gmail.com>,
        Andreas Hindborg <andreas@metaspace.dk>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Thu, Nov 3, 2022 at 7:12 AM Dennis Dai <dzy.0424thu@gmail.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