From: Tejun Heo <tj@kernel.org>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: linux-kernel@vger.kernel.org, Lai Jiangshan <jiangshanlai@gmail.com>
Subject: Re: [PATCH] workqueue: Correct declaration of cpu_pwq in struct workqueue_struct
Date: Mon, 5 Aug 2024 10:31:42 -1000 [thread overview]
Message-ID: <ZrE2rpXmGQ-P4kYE@slm.duckdns.org> (raw)
In-Reply-To: <20240805073037.60238-1-ubizjak@gmail.com>
On Mon, Aug 05, 2024 at 09:30:29AM +0200, Uros Bizjak wrote:
> cpu_pwq is used in various percpu functions that expect variable in
> __percpu address space. Correct the declaration of cpu_pwq to
>
> struct pool_workqueue __rcu * __percpu *cpu_pwq
>
> to declare the variable as __percpu pointer.
>
> The patch also fixes following sparse errors:
>
> workqueue.c:380:37: warning: duplicate [noderef]
> workqueue.c:380:37: error: multiple address spaces given: __rcu & __percpu
> workqueue.c:2271:15: error: incompatible types in comparison expression (different address spaces):
> workqueue.c:2271:15: struct pool_workqueue [noderef] __rcu *
> workqueue.c:2271:15: struct pool_workqueue [noderef] __percpu *
>
> and uncovers a couple of exisiting "incorrect type in assignment"
> warnings (from __rcu address space), which this patch does not address.
>
> Found by GCC's named address space checks.
>
> There were no changes in the resulting object files.
>
> Signed-off-by: Uros Bizjak <ubizjak@gmail.com>
> Cc: Tejun Heo <tj@kernel.org>
> Cc: Lai Jiangshan <jiangshanlai@gmail.com>
Applied to wq/for-6.11-fixes.
Thanks.
--
tejun
prev parent reply other threads:[~2024-08-05 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 7:30 Uros Bizjak
2024-08-05 20:31 ` Tejun Heo [this message]
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=ZrE2rpXmGQ-P4kYE@slm.duckdns.org \
--to=tj@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ubizjak@gmail.com \
/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®