diff options
| author | Georgios Androutsopoulos <georgeandrout13@gmail.com> | 2026-09-08 16:13:02 -0400 |
|---|---|---|
| committer | Yury Norov <ynorov@nvidia.com> | 2026-10-06 12:15:40 -0400 |
| commit | a73b4d1fa7d334a5f7de5bb0a14726530f66196e (patch) | |
| tree | e70914a6d6acaffbb806606c376a5ba80bad2b41 /include/linux | |
| parent | 842c5beca0b369bb143b86d6ae63dbcd7c5f0988 (diff) | |
| download | linux-next-a73b4d1fa7d334a5f7de5bb0a14726530f66196e.tar.gz linux-next-a73b4d1fa7d334a5f7de5bb0a14726530f66196e.zip | |
rust: bitmap: document panics in `next_bit` and `next_zero_bit`
`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.
Update the documentation of `next_bit()` and `next_zero_bit()` to add
the missing `# Panics` sections, add the missing blank doc comment line
before `Returns` in `next_zero_bit()`, and simplify the wording.
Fixes: 11eca92a2cae ("rust: add bitmap API.")
Closes: https://github.com/Rust-for-Linux/linux/issues/1252
Reviewed-by: Alexandre Courbot <acourbot@nvidia.com>
Signed-off-by: Georgios Androutsopoulos <georgeandrout13@gmail.com>
Signed-off-by: Yury Norov <ynorov@nvidia.com>
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions
