[PATCH] rust: num: bounded: add safety comment for Bounded::__new
From: Hsiu Che Yu
Date: Mon Dec 01 2025 - 01:26:12 EST
The `__new` constructor only performs a bounds check and stores the
value in the wrapper type. It does not perform any unsafe memory
operations, so it does not need to be marked as `unsafe`.
Reported-by: Miguel Ojeda <ojeda@xxxxxxxxxx>
Closes: https://github.com/Rust-for-Linux/linux/issues/1211
Signed-off-by: Hsiu Che Yu <yu.whisper.personal@xxxxxxxxx>
---
rust/kernel/num/bounded.rs | 3 +++
1 file changed, 3 insertions(+)
diff --git a/rust/kernel/num/bounded.rs b/rust/kernel/num/bounded.rs
index f870080af8ac..cde1b8ba6880 100644
--- a/rust/kernel/num/bounded.rs
+++ b/rust/kernel/num/bounded.rs
@@ -284,6 +284,9 @@ impl<T, const N: u32> Bounded<T, N>
///
/// The caller remains responsible for checking, either statically or dynamically, that `value`
/// can be represented as a `T` using at most `N` bits.
+ ///
+ /// **Note**: This function is not marked as `unsafe` because it performs no memory-unsafe
+ /// operations itself.
const fn __new(value: T) -> Self {
// Enforce the type invariants.
const {
--
2.43.0