Miguel Ojeda 6618d69aa1 rust: print: avoid evaluating arguments in pr_* macros in unsafe blocks ... At the moment it is possible to perform unsafe operations in the arguments of `pr_*` macros since they are evaluated inside an `unsafe` block: let x = &10u32 as *const u32; pr_info!("{}", *x); In other words, this is a soundness issue. Fix it so that it requires an explicit `unsafe` block. Reported-by: Wedson Almeida Filho <wedsonaf@gmail.com> Reported-by: Domen Puncer Kugler <domen.puncerkugler@nccgroup.com> Link: https://github.com/Rust-for-Linux/linux/issues/479 Signed-off-by: Miguel Ojeda <ojeda@kernel.org> Reviewed-by: Boqun Feng <boqun.feng@gmail.com> Reviewed-by: Gary Guo <gary@garyguo.net> Reviewed-by: Björn Roy Baron <bjorn3_gh@protonmail.com> Reviewed-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>		2023-01-16 00:54:35 +01:00
..
allocator.rs
build_assert.rs	rust: build_assert: add build_{error,assert}! macros	2022-12-04 01:59:16 +01:00
error.rs	rust: error: add From implementations for Error	2022-12-04 01:59:15 +01:00
lib.rs	rust: types: add Either type	2022-12-04 01:59:16 +01:00
prelude.rs	rust: build_assert: add build_{error,assert}! macros	2022-12-04 01:59:16 +01:00
print.rs	rust: print: avoid evaluating arguments in pr_* macros in unsafe blocks	2023-01-16 00:54:35 +01:00
static_assert.rs	rust: static_assert: add static_assert! macro	2022-12-04 01:59:16 +01:00
std_vendor.rs	rust: std_vendor: add dbg! macro based on std's one	2022-12-04 01:59:16 +01:00
str.rs	rust: str: add fmt! macro	2022-12-04 01:59:16 +01:00
types.rs	rust: types: add Opaque type	2022-12-04 01:59:16 +01:00