From: Alice Ryhl <aliceryhl@google.com>
To: Georgios Androutsopoulos <georgeandrout13@gmail.com>
Cc: "Burak Emir" <burak.emir@gmail.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Yury Norov" <yury.norov@gmail.com>,
"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Tamir Duberstein" <tamird@kernel.org>,
"Alexandre Courbot" <acourbot@nvidia.com>,
"Onur Özkan" <work@onurozkan.dev>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rust: bitmap: document panics in `next_bit` and `next_zero_bit`
Date: Fri, 28 Aug 2026 09:06:32 +0000 [thread overview]
Message-ID: <apFPmLLkH-FBXFdz@google.com> (raw)
In-Reply-To: <20260827150719.109145-1-georgeandrout13@gmail.com>
On Thu, Aug 27, 2026 at 11:07:19AM -0400, Georgios Androutsopoulos wrote:
> `next_bit()` and `next_zero_bit()` use `bitmap_assert!()` to check
> that `start` is less than `self.len()`, which panics when
> `CONFIG_RUST_BITMAP_HARDENED` is enabled. However, neither function
> has a `# Panics` section, and both document that `None` is returned
> for exactly the input that triggers the panic.
>
> Add the missing `# Panics` sections and condition the `None` case on
> `CONFIG_RUST_BITMAP_HARDENED` being disabled, matching the style used
> by `set_bit()`, `clear_bit()` and their atomic versions in the same
> file. Also add the missing blank doc comment line before `Returns` in
> `next_zero_bit()`.
>
> Link: https://github.com/Rust-for-Linux/linux/issues/1252
>
> Signed-off-by: Georgios Androutsopoulos <georgeandrout13@gmail.com>
There's an unncessary empty newline between Link: and Signed-off-by:
> rust/kernel/bitmap.rs | 17 +++++++++++++++--
> 1 file changed, 15 insertions(+), 2 deletions(-)
>
> diff --git a/rust/kernel/bitmap.rs b/rust/kernel/bitmap.rs
> index b27e0ec80..b33f7ce5c 100644
> --- a/rust/kernel/bitmap.rs
> +++ b/rust/kernel/bitmap.rs
> @@ -459,7 +459,13 @@ pub fn last_bit(&self) -> Option<usize> {
>
> /// Finds next set bit, starting from `start`.
> ///
> - /// Returns `None` if `start` is greater or equal to `self.nbits`.
> + /// If `CONFIG_RUST_BITMAP_HARDENED` is not enabled and `start` is greater
> + /// than or equal to `self.len()`, returns `None`.
> + ///
> + /// # Panics
> + ///
> + /// Panics if `CONFIG_RUST_BITMAP_HARDENED` is enabled and `start` is
> + /// greater than or equal to `self.len()`.
This wording is a bit repetetive. I think we can simplify to:
/// Finds next set bit, starting from `start`.
///
/// Returns `None` if no bits are set on or after the given index. The
/// index `start` must be in bounds.
///
/// # Panics
///
/// Panics if `CONFIG_RUST_BITMAP_HARDENED` is enabled and `start` is
/// out of bounds.
Alice
prev parent reply other threads:[~2026-08-28 9:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 15:07 [PATCH] rust: bitmap: document panics in `next_bit` and `next_zero_bit` Georgios Androutsopoulos
2026-08-28 9:06 ` Alice Ryhl [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=apFPmLLkH-FBXFdz@google.com \
--to=aliceryhl@google.com \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=burak.emir@gmail.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=gary@garyguo.net \
--cc=georgeandrout13@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@kernel.org \
--cc=tmgross@umich.edu \
--cc=work@onurozkan.dev \
--cc=yury.norov@gmail.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