From: FUJITA Tomonori <tomo@aliasing.net>
To: ojeda@kernel.org
Cc: a.hindborg@kernel.org, acourbot@nvidia.com, aliceryhl@google.com,
bjorn3_gh@protonmail.com, boqun@kernel.org, dakr@kernel.org,
daniel.almeida@collabora.com, gary@garyguo.net,
lossin@kernel.org, tamird@kernel.org, tmgross@umich.edu,
work@onurozkan.dev, rust-for-linux@vger.kernel.org,
FUJITA Tomonori <fujita.tomonori@gmail.com>
Subject: [PATCH v1] rust: bug: Add bug_on macro
Date: Tue, 7 Jul 2026 23:30:26 +0900 [thread overview]
Message-ID: <20260707143026.2774023-1-tomo@aliasing.net> (raw)
From: FUJITA Tomonori <fujita.tomonori@gmail.com>
Add bug_on macro(), the Rust equivalent of the C's BUG_ON(), which
uses the BUG/WARN feature (lib/bug.c) via assembly for
x86_64/arm64/riscv/s390 like warn_on() macro.
Use of this macro is heavily discouraged. Prefer warn_on() macro with
recovery code where feasible. See the documentation for C's BUG_ON()
for guidance on when it is rarely justified.
Signed-off-by: FUJITA Tomonori <fujita.tomonori@gmail.com>
---
rust/kernel/bug.rs | 105 ++++++++++++++++++++++++++++++++-------------
1 file changed, 76 insertions(+), 29 deletions(-)
diff --git a/rust/kernel/bug.rs b/rust/kernel/bug.rs
index ed943960f851..0f904c4614a2 100644
--- a/rust/kernel/bug.rs
+++ b/rust/kernel/bug.rs
@@ -11,9 +11,13 @@
#[cfg(all(CONFIG_BUG, not(CONFIG_UML), not(CONFIG_LOONGARCH), not(CONFIG_ARM)))]
#[cfg(CONFIG_DEBUG_BUGVERBOSE)]
macro_rules! warn_flags {
- ($file:expr, $flags:expr) => {
- const FLAGS: u32 = $crate::bindings::BUGFLAG_WARNING | $flags;
- const _FILE: &[u8] = $file.as_bytes();
+ ($cond:expr, $flags:expr, $asm_tail:expr) => {{
+ #[cfg(CONFIG_DEBUG_BUGVERBOSE_DETAILED)]
+ const _COND_STR: &str = concat!("[", stringify!($cond), "] ", file!());
+ #[cfg(not(CONFIG_DEBUG_BUGVERBOSE_DETAILED))]
+ const _COND_STR: &str = file!();
+
+ const _FILE: &[u8] = _COND_STR.as_bytes();
// Plus one for null-terminator.
static FILE: [u8; _FILE.len() + 1] = {
let mut bytes = [0; _FILE.len() + 1];
@@ -24,6 +28,7 @@ macro_rules! warn_flags {
}
bytes
};
+ const FLAGS: u32 = $flags;
// SAFETY:
// - `file`, `line`, `flags`, and `size` are all compile-time constants or
@@ -35,14 +40,14 @@ macro_rules! warn_flags {
concat!(
"/* {size} */",
include!(concat!(env!("OBJTREE"), "/rust/kernel/generated_arch_warn_asm.rs")),
- include!(concat!(env!("OBJTREE"), "/rust/kernel/generated_arch_reachable_asm.rs")));
+ $asm_tail);
file = sym FILE,
line = const line!(),
flags = const FLAGS,
size = const ::core::mem::size_of::<$crate::bindings::bug_entry>(),
);
}
- }
+ }};
}
#[macro_export]
@@ -50,8 +55,8 @@ macro_rules! warn_flags {
#[cfg(all(CONFIG_BUG, not(CONFIG_UML), not(CONFIG_LOONGARCH), not(CONFIG_ARM)))]
#[cfg(not(CONFIG_DEBUG_BUGVERBOSE))]
macro_rules! warn_flags {
- ($file:expr, $flags:expr) => {
- const FLAGS: u32 = $crate::bindings::BUGFLAG_WARNING | $flags;
+ ($cond:expr, $flags:expr, $asm_tail:expr) => {
+ const FLAGS: u32 = $flags;
// SAFETY:
// - `flags` and `size` are all compile-time constants, preventing
@@ -63,7 +68,7 @@ macro_rules! warn_flags {
concat!(
"/* {size} */",
include!(concat!(env!("OBJTREE"), "/rust/kernel/generated_arch_warn_asm.rs")),
- include!(concat!(env!("OBJTREE"), "/rust/kernel/generated_arch_reachable_asm.rs")));
+ $asm_tail);
flags = const FLAGS,
size = const ::core::mem::size_of::<$crate::bindings::bug_entry>(),
);
@@ -75,16 +80,23 @@ macro_rules! warn_flags {
#[doc(hidden)]
#[cfg(all(CONFIG_BUG, CONFIG_UML))]
macro_rules! warn_flags {
- ($file:expr, $flags:expr) => {
- // SAFETY: It is always safe to call `warn_slowpath_fmt()`
- // with a valid null-terminated string.
- unsafe {
- $crate::bindings::warn_slowpath_fmt(
- $crate::c_str!(::core::file!()).as_char_ptr(),
- line!() as $crate::ffi::c_int,
- $flags as $crate::ffi::c_uint,
- ::core::ptr::null(),
- );
+ ($cond:expr, $flags:expr, $asm_tail:expr) => {
+ // bug_on!() sets $flags to 0, so we can use that to determine
+ // whether to call BUG() or WARN_ON().
+ if $flags == 0 {
+ // SAFETY: It is always safe to call `BUG()`.
+ unsafe { $crate::bindings::BUG() }
+ } else {
+ // SAFETY: It is always safe to call `warn_slowpath_fmt()`
+ // with a valid null-terminated string.
+ unsafe {
+ $crate::bindings::warn_slowpath_fmt(
+ $crate::c_str!(::core::file!()).as_char_ptr(),
+ line!() as $crate::ffi::c_int,
+ $flags as $crate::ffi::c_uint,
+ ::core::ptr::null(),
+ );
+ }
}
};
}
@@ -93,9 +105,16 @@ macro_rules! warn_flags {
#[doc(hidden)]
#[cfg(all(CONFIG_BUG, any(CONFIG_LOONGARCH, CONFIG_ARM)))]
macro_rules! warn_flags {
- ($file:expr, $flags:expr) => {
- // SAFETY: It is always safe to call `WARN_ON()`.
- unsafe { $crate::bindings::WARN_ON(true) }
+ ($cond:expr, $flags:expr, $asm_tail:expr) => {
+ // bug_on!() sets $flags to 0, so we can use that to determine
+ // whether to call BUG() or WARN_ON().
+ if $flags == 0 {
+ // SAFETY: It is always safe to call `BUG()`.
+ unsafe { $crate::bindings::BUG() }
+ } else {
+ // SAFETY: It is always safe to call `WARN_ON()`.
+ unsafe { $crate::bindings::WARN_ON(true) }
+ }
};
}
@@ -103,7 +122,7 @@ macro_rules! warn_flags {
#[doc(hidden)]
#[cfg(not(CONFIG_BUG))]
macro_rules! warn_flags {
- ($file:expr, $flags:expr) => {};
+ ($cond:expr, $flags:expr, $asm_tail:expr) => {};
}
#[doc(hidden)]
@@ -117,16 +136,44 @@ macro_rules! warn_on {
($cond:expr) => {{
let cond = $cond;
- #[cfg(CONFIG_DEBUG_BUGVERBOSE_DETAILED)]
- const _COND_STR: &str = concat!("[", stringify!($cond), "] ", file!());
- #[cfg(not(CONFIG_DEBUG_BUGVERBOSE_DETAILED))]
- const _COND_STR: &str = file!();
-
if cond {
- const WARN_ON_FLAGS: u32 = $crate::bug::bugflag_taint($crate::bindings::TAINT_WARN);
+ #[cfg(any(not(CONFIG_BUG), CONFIG_UML))]
+ const WARN_ON_FLAGS: u32 = $crate::bindings::TAINT_WARN;
+ #[cfg(all(CONFIG_BUG, not(CONFIG_UML)))]
+ const WARN_ON_FLAGS: u32 = $crate::bindings::BUGFLAG_WARNING
+ | $crate::bug::bugflag_taint($crate::bindings::TAINT_WARN);
- $crate::warn_flags!(_COND_STR, WARN_ON_FLAGS);
+ $crate::warn_flags!(
+ $cond,
+ WARN_ON_FLAGS,
+ include!(concat!(
+ env!("OBJTREE"),
+ "/rust/kernel/generated_arch_reachable_asm.rs"
+ ))
+ );
}
cond
}};
}
+
+/// Reports an unrecoverable kernel bug if `cond` is true.
+///
+/// This is the Rust equivalent of the C macro [`BUG_ON()`]. Unlike [`warn_on!`], it never
+/// returns control to the caller when `cond` is true.
+///
+/// Use of this macro is *heavily discouraged*. Prefer [`warn_on!`] with recovery code where
+/// feasible. Please see the documentation for the C macro [`BUG_ON()`] for guidance on when it
+/// is (rarely) justified.
+///
+/// [`BUG_ON()`]: https://docs.kernel.org/process/deprecated.html#bug-and-bug-on
+#[macro_export]
+macro_rules! bug_on {
+ ($cond:expr) => {{
+ let cond = $cond;
+ if cond {
+ $crate::warn_flags!($cond, 0, "");
+ // SAFETY: We call `BUG()` above so this block will never be reached.
+ unsafe { core::hint::unreachable_unchecked() }
+ }
+ }};
+}
base-commit: dc59e4fea9d83f03bad6bddf3fa2e52491777482
--
2.43.0
next reply other threads:[~2026-07-07 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 14:30 FUJITA Tomonori [this message]
2026-07-07 14:51 ` [PATCH v1] rust: bug: Add bug_on macro Danilo Krummrich
2026-07-07 15:20 ` Greg KH
2026-07-07 22:48 ` FUJITA Tomonori
2026-07-08 5:29 ` Greg KH
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=20260707143026.2774023-1-tomo@aliasing.net \
--to=tomo@aliasing.net \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--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 \
/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