From: Lukasz Luba <lukasz.luba@arm.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
Subject: Re: [PATCH v2] PM: EM: Address RCU-related sparse warnings
Date: Fri, 7 Mar 2025 13:02:50 +0000 [thread overview]
Message-ID: <4a538376-bf74-4c51-bfa8-a86f67790662@arm.com> (raw)
In-Reply-To: <5885405.DvuYhMxLoT@rjwysocki.net>
On 3/6/25 16:49, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> The usage of __rcu in the Energy Model code is quite inconsistent
> which causes the following sparse warnings to trigger:
>
> kernel/power/energy_model.c:169:15: warning: incorrect type in assignment (different address spaces)
> kernel/power/energy_model.c:169:15: expected struct em_perf_table [noderef] __rcu *table
> kernel/power/energy_model.c:169:15: got struct em_perf_table *
> kernel/power/energy_model.c:171:9: warning: incorrect type in argument 1 (different address spaces)
> kernel/power/energy_model.c:171:9: expected struct callback_head *head
> kernel/power/energy_model.c:171:9: got struct callback_head [noderef] __rcu *
> kernel/power/energy_model.c:171:9: warning: cast removes address space '__rcu' of expression
> kernel/power/energy_model.c:182:19: warning: incorrect type in argument 1 (different address spaces)
> kernel/power/energy_model.c:182:19: expected struct kref *kref
> kernel/power/energy_model.c:182:19: got struct kref [noderef] __rcu *
> kernel/power/energy_model.c:200:15: warning: incorrect type in assignment (different address spaces)
> kernel/power/energy_model.c:200:15: expected struct em_perf_table [noderef] __rcu *table
> kernel/power/energy_model.c:200:15: got void *[assigned] _res
> kernel/power/energy_model.c:204:20: warning: incorrect type in argument 1 (different address spaces)
> kernel/power/energy_model.c:204:20: expected struct kref *kref
> kernel/power/energy_model.c:204:20: got struct kref [noderef] __rcu *
> kernel/power/energy_model.c:320:19: warning: incorrect type in argument 1 (different address spaces)
> kernel/power/energy_model.c:320:19: expected struct kref *kref
> kernel/power/energy_model.c:320:19: got struct kref [noderef] __rcu *
> kernel/power/energy_model.c:325:45: warning: incorrect type in argument 2 (different address spaces)
> kernel/power/energy_model.c:325:45: expected struct em_perf_state *table
> kernel/power/energy_model.c:325:45: got struct em_perf_state [noderef] __rcu *
> kernel/power/energy_model.c:425:45: warning: incorrect type in argument 3 (different address spaces)
> kernel/power/energy_model.c:425:45: expected struct em_perf_state *table
> kernel/power/energy_model.c:425:45: got struct em_perf_state [noderef] __rcu *
> kernel/power/energy_model.c:442:15: warning: incorrect type in argument 1 (different address spaces)
> kernel/power/energy_model.c:442:15: expected void const *objp
> kernel/power/energy_model.c:442:15: got struct em_perf_table [noderef] __rcu *[assigned] em_table
> kernel/power/energy_model.c:626:55: warning: incorrect type in argument 2 (different address spaces)
> kernel/power/energy_model.c:626:55: expected struct em_perf_state *table
> kernel/power/energy_model.c:626:55: got struct em_perf_state [noderef] __rcu *
> kernel/power/energy_model.c:681:16: warning: incorrect type in assignment (different address spaces)
> kernel/power/energy_model.c:681:16: expected struct em_perf_state *new_ps
> kernel/power/energy_model.c:681:16: got struct em_perf_state [noderef] __rcu *
> kernel/power/energy_model.c:699:37: warning: incorrect type in argument 2 (different address spaces)
> kernel/power/energy_model.c:699:37: expected struct em_perf_state *table
> kernel/power/energy_model.c:699:37: got struct em_perf_state [noderef] __rcu *
> kernel/power/energy_model.c:733:38: warning: incorrect type in argument 3 (different address spaces)
> kernel/power/energy_model.c:733:38: expected struct em_perf_state *table
> kernel/power/energy_model.c:733:38: got struct em_perf_state [noderef] __rcu *
> kernel/power/energy_model.c:855:53: warning: dereference of noderef expression
> kernel/power/energy_model.c:864:32: warning: dereference of noderef expression
>
> This is because the __rcu annotation for sparse is only applicable to
> pointers that need rcu_dereference() or equivalent for protection, which
> basically means pointers assigned with rcu_assign_pointer().
>
> Make all of the above sparse warnings go away by cleaning up the usage
> of __rcu and using rcu_dereference_protected() where applicable.
>
> Cc: All applicable <stable@vger.kernel.org>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> ---
>
> This replaces
>
> https://lore.kernel.org/linux-pm/1929404.tdWV9SEqCh@rjwysocki.net/
>
> and
>
> https://lore.kernel.org/linux-pm/13728396.uLZWGnKmhe@rjwysocki.net/
>
> ---
> include/linux/energy_model.h | 12 ++++++------
> kernel/power/energy_model.c | 39 ++++++++++++++++++++-------------------
> 2 files changed, 26 insertions(+), 25 deletions(-)
>
LGTM,
Reviewed-by: Lukasz Luba <lukasz.luba@arm.com>
prev parent reply other threads:[~2025-03-07 13:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 16:49 Rafael J. Wysocki
2025-03-07 13:02 ` Lukasz Luba [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=4a538376-bf74-4c51-bfa8-a86f67790662@arm.com \
--to=lukasz.luba@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=ricardo.neri-calderon@linux.intel.com \
--cc=rjw@rjwysocki.net \
/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®