From: FUJITA Tomonori <tomo@flapping.org>
To: aliceryhl@google.com, ojeda@kernel.org, rostedt@goodmis.org
Cc: a.hindborg@kernel.org, acourbot@nvidia.com,
bjorn3_gh@protonmail.com, boqun@kernel.org, dakr@kernel.org,
daniel.almeida@collabora.com, gary@garyguo.net,
lossin@kernel.org, mathieu.desnoyers@efficios.com,
mhiramat@kernel.org, tamird@kernel.org, tmgross@umich.edu,
work@onurozkan.dev, linux-trace-kernel@vger.kernel.org,
rust-for-linux@vger.kernel.org,
FUJITA Tomonori <fujita.tomonori@gmail.com>
Subject: [PATCH v1] rust: add mark_used macro
Date: Mon, 10 Aug 2026 16:51:44 +0900 [thread overview]
Message-ID: <20260810075144.1245761-1-tomo@flapping.org> (raw)
From: FUJITA Tomonori <fujita.tomonori@gmail.com>
Macros whose expansion depends on the kernel configuration end up
ignoring some of their arguments, resulting in unused warnings.
Add a macro for the `if false { _ = ...; }` idiom used to avoid them,
and convert the existing open-coded users in `warn_flags!` and
`declare_trace!`.
Signed-off-by: FUJITA Tomonori <fujita.tomonori@gmail.com>
---
rust/kernel/bug.rs | 18 ++++--------------
rust/kernel/lib.rs | 12 ++++++++++++
rust/kernel/tracepoint.rs | 5 ++---
3 files changed, 18 insertions(+), 17 deletions(-)
diff --git a/rust/kernel/bug.rs b/rust/kernel/bug.rs
index 3566f0234ca4..c1e4eb7d4a70 100644
--- a/rust/kernel/bug.rs
+++ b/rust/kernel/bug.rs
@@ -55,9 +55,7 @@ macro_rules! warn_flags {
($file:expr, $flags:expr) => {
const FLAGS: u32 = $crate::bindings::BUGFLAG_WARNING | $flags;
- if false {
- _ = $file;
- }
+ $crate::mark_used!($file);
// SAFETY:
// - `flags` and `size` are all compile-time constants, preventing
@@ -83,9 +81,7 @@ macro_rules! warn_flags {
#[cfg(all(CONFIG_BUG, CONFIG_UML))]
macro_rules! warn_flags {
($file:expr, $flags:expr) => {
- if false {
- _ = $file;
- }
+ $crate::mark_used!($file);
// SAFETY: It is always safe to call `warn_slowpath_fmt()`
// with a valid null-terminated string.
@@ -106,10 +102,7 @@ macro_rules! warn_flags {
#[cfg(all(CONFIG_BUG, any(CONFIG_LOONGARCH, CONFIG_ARM)))]
macro_rules! warn_flags {
($file:expr, $flags:expr) => {
- if false {
- _ = $file;
- _ = $flags;
- }
+ $crate::mark_used!($file, $flags);
// SAFETY: It is always safe to call `WARN_ON()`.
unsafe { $crate::bindings::WARN_ON(true) }
@@ -121,10 +114,7 @@ macro_rules! warn_flags {
#[cfg(any(testlib, not(CONFIG_BUG)))]
macro_rules! warn_flags {
($file:expr, $flags:expr) => {
- if false {
- _ = $file;
- _ = $flags;
- }
+ $crate::mark_used!($file, $flags);
};
}
diff --git a/rust/kernel/lib.rs b/rust/kernel/lib.rs
index 9512af7156df..2f770d80bd8a 100644
--- a/rust/kernel/lib.rs
+++ b/rust/kernel/lib.rs
@@ -266,6 +266,18 @@ macro_rules! container_of {
#[doc(hidden)]
pub fn assert_same_type<T>(_: T, _: T) {}
+/// Marks the given expressions as used.
+///
+/// This avoids "unused" warnings in kernel configurations that do not otherwise use them.
+#[macro_export]
+macro_rules! mark_used {
+ ($($e:expr),* $(,)?) => {
+ if false {
+ $( _ = $e; )*
+ }
+ };
+}
+
/// Helper for `.rs.S` files.
#[doc(hidden)]
#[macro_export]
diff --git a/rust/kernel/tracepoint.rs b/rust/kernel/tracepoint.rs
index c6e80aa99e8e..cb06fec4c4d9 100644
--- a/rust/kernel/tracepoint.rs
+++ b/rust/kernel/tracepoint.rs
@@ -38,9 +38,8 @@ macro_rules! declare_trace {
#[cfg(not(CONFIG_TRACEPOINTS))]
{
- // If tracepoints are disabled, insert a trivial use of each argument
- // to avoid unused argument warnings.
- $( let _unused = $argname; )*
+ // If tracepoints are disabled, the arguments are unused.
+ $crate::mark_used!($($argname),*);
}
}
)*}
base-commit: d8973c47544371613313ecb9a8c3e7b244aa9bbf
--
2.43.0
next reply other threads:[~2026-08-10 7:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 7:51 FUJITA Tomonori [this message]
2026-08-10 10:41 ` [PATCH v1] rust: add mark_used macro Gary Guo
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=20260810075144.1245761-1-tomo@flapping.org \
--to=tomo@flapping.org \
--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=linux-trace-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=ojeda@kernel.org \
--cc=rostedt@goodmis.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