From: Andreas Hindborg <a.hindborg@kernel.org>
To: Wenzhao Liao <wenzhaoliao@ruc.edu.cn>,
Jens Axboe <axboe@kernel.dk>, Miguel Ojeda <ojeda@kernel.org>,
linux-block@vger.kernel.org, rust-for-linux@vger.kernel.org
Cc: "Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/2] rust: block: safely abstract the blk-mq poll callback
Date: Sat, 11 Apr 2026 12:33:38 +0200 [thread overview]
Message-ID: <87ik9xwzul.fsf@kernel.org> (raw)
In-Reply-To: <20260410191544.2203201-1-wenzhaoliao@ruc.edu.cn>
"Wenzhao Liao" <wenzhaoliao@ruc.edu.cn> writes:
> Rust blk-mq drivers currently cannot implement the `blk_mq_ops->poll`
> callback: the Rust vtable hardcodes `poll: None`, and there is no safe
> way for a driver to receive the borrowed hardware queue context or the
> optional completion batch pointer that blk-mq passes to C drivers.
Again, this is covered by the series at [1]. Please instruct your AI agent
to read that thread before submitting more patches.
Best regards,
Andreas Hindborg
[1] https://lore.kernel.org/rust-for-linux/20260216-rnull-v6-19-rc5-send-v1-0-de9a7af4b469@kernel.org/
prev parent reply other threads:[~2026-04-11 10:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <34Y9hHd4E8CdmCmv6LKr2tXYoUyzhgpwOGgK88jxj_B5UHGX-NM-7g0Wr3PXLWBlF0lzMM8lcS_LHtoQAGVn7g==@protonmail.internalid>
2026-04-10 19:15 ` [RFC PATCH 0/2] rust: block: safely abstract the blk-mq poll callback Wenzhao Liao
2026-04-10 19:15 ` [RFC PATCH 1/2] rust: block: mq: safely abstract the " Wenzhao Liao
2026-04-10 19:15 ` [RFC PATCH 2/2] block: rnull: wire up poll queues dummy callback Wenzhao Liao
2026-04-11 10:33 ` Andreas Hindborg [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=87ik9xwzul.fsf@kernel.org \
--to=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=axboe@kernel.dk \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=wenzhaoliao@ruc.edu.cn \
/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