From: Miguel Ojeda <ojeda@kernel.org>
To: penguin-kernel@i-love.sakura.ne.jp
Cc: akpm@linux-foundation.org, axboe@kernel.dk, bvanassche@acm.org,
dlemoal@kernel.org, hch@lst.de, hdanton@sina.com,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
ojeda@kernel.org, tom.leiming@gmail.com, wqu@suse.com,
Andreas Hindborg <a.hindborg@kernel.org>,
Boqun Feng <boqun@kernel.org>,
rust-for-linux@vger.kernel.org, Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH v3] block: assign caller-specific lockdep class to disk->open_mutex
Date: Thu, 4 Jun 2026 23:07:04 +0200 [thread overview]
Message-ID: <20260604210704.41751-1-ojeda@kernel.org> (raw)
In-Reply-To: <226152a3-1e4c-4eec-9a17-1d40426a7b18@I-love.SAKURA.ne.jp>
On Wed, 03 Jun 2026 20:54:05 +0900 Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp> wrote:
>
> Acknowledgment:
> Since I have no experience with Rust, changes needed by Rust block layer
> bindings and rnull module are made based on conversation with the Gemini
> AI collaborator.
Then please do Cc the right people as `MAINTAINERS` mentions, including
"BLOCK LAYER DEVICE DRIVER API [RUST]" and "RUST"...
I am quite confused. Why was this added to linux-next?
It doesn't go through block, nor has an Ack or review and breaks
the `rustdoc` build in linux-next (and thus rust.docs.kernel.org):
error: unresolved link to `my_gendisk_lkclass`
--> rust/kernel/block/mq/gen_disk.rs:42:50
|
42 | /// This type can only be instantiated via the [`my_gendisk_lkclass!`] macro.
It is also not Clippy-clean -- it doesn't follow our usual conventions
for safety comments and sections:
error: unsafe function's docs are missing a `# Safety` section
--> rust/kernel/block/mq/gen_disk.rs:59:5
|
59 | pub const unsafe fn new_lock_class(ptr: *mut bindings::gendisk_lkclass) -> GenDiskLockClass {
error: function has unnecessary safety comment
--> rust/kernel/block/mq/gen_disk.rs:59:5
|
58 | /// SAFETY: `ptr` must point to a valid static `gendisk_lkclass` instance.
| ------- help: consider changing it to a `# Safety` section: `# Safety`
59 | pub const unsafe fn new_lock_class(ptr: *mut bindings::gendisk_lkclass) -> GenDiskLockClass {
Please see:
https://rust-for-linux.com/contributing#submit-checklist-addendum
In any case, it is also too late in the cycle to be experimenting in
linux-next.
So what am I missing? What is going on?
(And on top of all that, for some reason I did not receive it even if I
am apparently in Cc, so I have asked the admins about that.)
Cheers,
Miguel
Cc: Andreas Hindborg <a.hindborg@kernel.org>
Cc: Boqun Feng <boqun@kernel.org>
Cc: rust-for-linux@vger.kernel.org
Cc: Mark Brown <broonie@kernel.org>
next prev parent reply other threads:[~2026-06-04 21:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-30 13:45 [PATCH] block: assign caller-specific lockdep class to disk->open_mutex Tetsuo Handa
2026-05-30 21:15 ` Bart Van Assche
2026-06-01 7:11 ` Christoph Hellwig
2026-06-03 6:25 ` [PATCH v2] " Tetsuo Handa
2026-06-03 11:54 ` [PATCH v3] " Tetsuo Handa
2026-06-04 21:07 ` Miguel Ojeda [this message]
2026-06-05 7:36 ` Andreas Hindborg
2026-06-05 10:08 ` Tetsuo Handa
2026-06-05 11:02 ` Miguel Ojeda
2026-06-05 12:04 ` Mark Brown
2026-06-05 12:40 ` Miguel Ojeda
2026-06-05 13:03 ` Mark Brown
2026-06-05 15:04 ` Mark Brown
2026-06-05 7:54 ` Andreas Hindborg
2026-06-05 10:14 ` Tetsuo Handa
2026-05-30 22:50 ` [PATCH] " Hillf Danton
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=20260604210704.41751-1-ojeda@kernel.org \
--to=ojeda@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=boqun@kernel.org \
--cc=broonie@kernel.org \
--cc=bvanassche@acm.org \
--cc=dlemoal@kernel.org \
--cc=hch@lst.de \
--cc=hdanton@sina.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=rust-for-linux@vger.kernel.org \
--cc=tom.leiming@gmail.com \
--cc=wqu@suse.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