From: Gary Guo <gary@garyguo.net>
To: FUJITA Tomonori <fujita.tomonori@gmail.com>
Cc: ojeda@kernel.org, a.hindborg@kernel.org, aliceryhl@google.com,
bjorn3_gh@protonmail.com, boqun.feng@gmail.com, dakr@kernel.org,
lossin@kernel.org, rust-for-linux@vger.kernel.org,
tmgross@umich.edu
Subject: Re: [PATCH v1] rust: bug: Support DEBUG_BUGVERBOSE_DETAILED option
Date: Wed, 7 Jan 2026 16:53:44 +0000 [thread overview]
Message-ID: <20260107165344.4e928ab4.gary@garyguo.net> (raw)
In-Reply-To: <20251204223405.454920-1-fujita.tomonori@gmail.com>
On Fri, 5 Dec 2025 07:34:05 +0900
FUJITA Tomonori <fujita.tomonori@gmail.com> wrote:
> Make warn_on() support DEBUG_BUGVERBOSE_DETAILED option, which was
> introduced by the commit aec58b48517c ("bugs/core: Extend
> __WARN_FLAGS() with the 'cond_str' parameter").
>
> When the option is enabled, WARN splats now show the evaluated
> warn_on() condition alongside the file path, e.g.:
>
> ------------[ cut here ]------------
> WARNING: [val == 1] /linux/samples/rust/rust_minimal.rs:27 at _RNvXCsk7t4azzUqHP_12rust_minimalNtB2_11RustMinimalNtCs8pcx3n4
> Modules linked in: rust_minimal(+)
>
> Signed-off-by: FUJITA Tomonori <fujita.tomonori@gmail.com>
> ---
> rust/kernel/bug.rs | 27 ++++++++++++++++-----------
> 1 file changed, 16 insertions(+), 11 deletions(-)
>
> diff --git a/rust/kernel/bug.rs b/rust/kernel/bug.rs
> index 36aef43e5ebe..a60db1ef4b48 100644
> --- a/rust/kernel/bug.rs
> +++ b/rust/kernel/bug.rs
> @@ -11,15 +11,14 @@
> #[cfg(all(CONFIG_BUG, not(CONFIG_UML), not(CONFIG_LOONGARCH), not(CONFIG_ARM)))]
> #[cfg(CONFIG_DEBUG_BUGVERBOSE)]
> macro_rules! warn_flags {
> - ($flags:expr) => {
> + ($file:expr, $flags:expr) => {
> const FLAGS: u32 = $crate::bindings::BUGFLAG_WARNING | $flags;
> - const _FILE: &[u8] = file!().as_bytes();
I think it'll be good to still keep
const _FILE: &[u8] = $file.as_bytes();
and have the caller just pass in `file!()` or `concat!(...)`. At least the
concat macro doesn't have to expanded multiple times in below.
Best,
Gary
> // Plus one for null-terminator.
> - static FILE: [u8; _FILE.len() + 1] = {
> - let mut bytes = [0; _FILE.len() + 1];
> + static FILE: [u8; $file.len() + 1] = {
> + let mut bytes = [0; $file.len() + 1];
> let mut i = 0;
> - while i < _FILE.len() {
> - bytes[i] = _FILE[i];
> + while i < $file.len() {
> + bytes[i] = $file[i];
> i += 1;
> }
> bytes
> @@ -50,7 +49,7 @@ 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 {
> - ($flags:expr) => {
> + ($file:expr, $flags:expr) => {
> const FLAGS: u32 = $crate::bindings::BUGFLAG_WARNING | $flags;
>
> // SAFETY:
> @@ -75,7 +74,7 @@ macro_rules! warn_flags {
> #[doc(hidden)]
> #[cfg(all(CONFIG_BUG, CONFIG_UML))]
> macro_rules! warn_flags {
> - ($flags:expr) => {
> + ($file:expr, $flags:expr) => {
> // SAFETY: It is always safe to call `warn_slowpath_fmt()`
> // with a valid null-terminated string.
> unsafe {
> @@ -93,7 +92,7 @@ macro_rules! warn_flags {
> #[doc(hidden)]
> #[cfg(all(CONFIG_BUG, any(CONFIG_LOONGARCH, CONFIG_ARM)))]
> macro_rules! warn_flags {
> - ($flags:expr) => {
> + ($file:expr, $flags:expr) => {
> // SAFETY: It is always safe to call `WARN_ON()`.
> unsafe { $crate::bindings::WARN_ON(true) }
> };
> @@ -103,7 +102,7 @@ macro_rules! warn_flags {
> #[doc(hidden)]
> #[cfg(not(CONFIG_BUG))]
> macro_rules! warn_flags {
> - ($flags:expr) => {};
> + ($file:expr, $flags:expr) => {};
> }
>
> #[doc(hidden)]
> @@ -116,10 +115,16 @@ pub const fn bugflag_taint(value: u32) -> u32 {
> macro_rules! warn_on {
> ($cond:expr) => {{
> let cond = $cond;
> +
> + #[cfg(CONFIG_DEBUG_BUGVERBOSE_DETAILED)]
> + const _COND_STR: &[u8] = concat!("[", stringify!($cond), "] ", file!()).as_bytes();
> + #[cfg(not(CONFIG_DEBUG_BUGVERBOSE_DETAILED))]
> + const _COND_STR: &[u8] = file!().as_bytes();
> +
> if cond {
> const WARN_ON_FLAGS: u32 = $crate::bug::bugflag_taint($crate::bindings::TAINT_WARN);
>
> - $crate::warn_flags!(WARN_ON_FLAGS);
> + $crate::warn_flags!(_COND_STR, WARN_ON_FLAGS);
> }
> cond
> }};
>
> base-commit: 500920fa76819b4909a32081e153bce80ce74824
next prev parent reply other threads:[~2026-01-07 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 22:34 [PATCH v1] rust: bug: Support DEBUG_BUGVERBOSE_DETAILED option FUJITA Tomonori
2026-01-07 16:53 ` Gary Guo [this message]
2026-01-08 1:22 ` FUJITA Tomonori
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=20260107165344.4e928ab4.gary@garyguo.net \
--to=gary@garyguo.net \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=fujita.tomonori@gmail.com \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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