From: Joe Perches <joe@perches.com>
To: Marco Crivellari <marco.crivellari@suse.com>,
linux-kernel@vger.kernel.org
Cc: Andy Whitcroft <apw@canonical.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>,
Michal Hocko <mhocko@suse.com>, Breno Leitao <leitao@debian.org>
Subject: Re: [PATCH v2] checkpatch: Check WQ_PERCPU or WQ_UNBOUND presence in alloc_workqueue() users
Date: Thu, 04 Jun 2026 10:11:48 -0700 [thread overview]
Message-ID: <aef9f10e1ee0e08928644e52cb0ebf50cdb2ce76.camel@perches.com> (raw)
In-Reply-To: <20260604154447.381477-1-marco.crivellari@suse.com>
On Thu, 2026-06-04 at 17:44 +0200, Marco Crivellari wrote:
> 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 an ERROR 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
[]
> diff --git 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)/) {
Align to open paren please
> +
> + 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);
> + ERROR("ALLOC_WORKQUEUE_FLAGS",
> + $error_msg . $herectx);
Align to open paren please
And as there are false positives, this should probably be a WARN
next prev parent reply other threads:[~2026-06-04 17:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 15:44 Marco Crivellari
2026-06-04 17:11 ` Joe Perches [this message]
2026-06-05 7:42 ` Marco Crivellari
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=aef9f10e1ee0e08928644e52cb0ebf50cdb2ce76.camel@perches.com \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=bigeasy@linutronix.de \
--cc=dwaipayanray1@gmail.com \
--cc=frederic@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=marco.crivellari@suse.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®