From: Marco Crivellari <marco.crivellari@suse.com>
To: linux-kernel@vger.kernel.org
Cc: Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Tejun Heo <tj@kernel.org>,
Frederic Weisbecker <frederic@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Marco Crivellari <marco.crivellari@suse.com>,
Michal Hocko <mhocko@suse.com>, Breno Leitao <leitao@debian.org>
Subject: [PATCH v5] checkpatch: Check WQ_PERCPU or WQ_UNBOUND presence in alloc_workqueue() users
Date: Mon, 8 Jun 2026 14:37:00 +0200 [thread overview]
Message-ID: <20260608123700.195206-1-marco.crivellari@suse.com> (raw)
The workqueue API introduced a new flag, WQ_PERCPU, that has to be used when
WQ_UNBOUND is not present. One of these flags must be present, but not
both of them.
To limit usage mistakes, emit a WARNING if one of the below condition is met:
- alloc_workqueue() is called without WQ_PERCPU nor WQ_UNBOUND
- alloc_workqueue() is called with both WQ_PERCPU and WQ_UNBOUND
Signed-off-by: Marco Crivellari <marco.crivellari@suse.com>
---
Changes in v5:
- Fixed "emit an ERROR" with "emit a WARNING" in the commit log
Link to v4: https://lore.kernel.org/all/20260608083711.76885-1-marco.crivellari@suse.com/
Changes in v4:
- properly align code
Link to v3: https://lore.kernel.org/all/20260605074309.49270-1-marco.crivellari@suse.com/
Changes in v3:
- code aligned to open parens
- ERROR changed with WARN
Link to v2: https://lore.kernel.org/all/20260604154447.381477-1-marco.crivellari@suse.com/
Changes in v2:
- removed $line from the test (Joe Perches)
- devm_alloc_workqueue() regex take into account also (Joe Perches)
- defined() on variables and other improvements (Joe Perches)
Link to v1: https://lore.kernel.org/all/20260603140941.320063-1-marco.crivellari@suse.com/
scripts/checkpatch.pl | 25 ++++++++++++++++++++++++-
1 file changed, 24 insertions(+), 1 deletion(-)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 0492d6afc9a1..52da2dc4f467 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -7804,8 +7804,31 @@ sub process {
ERROR("UNINITIALIZED_PTR_WITH_FREE",
"pointer '$1' with __free attribute should be initialized\n" . $herecurr);
}
- }
+# check alloc_workqueue() parameters for WQ_PERCPU and WQ_UNBOUND uses
+ if (defined($stat) &&
+ $stat =~ /^[ \+]\s*(?:$Lval\s*=\s*)?((?:devm_)?alloc_workqueue)\s*($balanced_parens)/) {
+
+ my $func = $1;
+ my $args = $2;
+ my $has_percpu = $args =~ /\bWQ_PERCPU\b/;
+ my $has_unbound = $args =~ /\bWQ_UNBOUND\b/;
+ my $error_msg;
+
+ if ($has_percpu && $has_unbound) {
+ $error_msg = "$func() should not contain both WQ_PERCPU and WQ_UNBOUND\n";
+ } elsif (!$has_percpu && !$has_unbound) {
+ $error_msg = "$func() must specify either WQ_PERCPU or WQ_UNBOUND\n";
+ }
+
+ if (defined($error_msg)) {
+ my $stmt_cnt = statement_rawlines($stat);
+ my $herectx = get_stat_here($linenr, $stmt_cnt, $here);
+ WARN("ALLOC_WORKQUEUE_FLAGS",
+ $error_msg . $herectx);
+ }
+ }
+ }
# If we have no input at all, then there is nothing to report on
# so just keep quiet.
if ($#rawlines == -1) {
--
2.54.0
reply other threads:[~2026-06-08 12:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260608123700.195206-1-marco.crivellari@suse.com \
--to=marco.crivellari@suse.com \
--cc=apw@canonical.com \
--cc=bigeasy@linutronix.de \
--cc=dwaipayanray1@gmail.com \
--cc=frederic@kernel.org \
--cc=joe@perches.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=mhocko@suse.com \
--cc=tj@kernel.org \
/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
all inboxes | Powered by JetHome®