[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8571bb0e-7f5a-4fd6-80f1-6b66b5110488@linux.intel.com>
Date: Thu, 12 Sep 2024 10:52:16 -0400
From: "Liang, Kan" <kan.liang@...ux.intel.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, Peter Zijlstra <peterz@...radead.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build warning after merge of the tip tree
On 2024-09-11 1:38 a.m., Stephen Rothwell wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> kernel/events/core.c: In function 'perf_event_setup_cpumask':
> kernel/events/core.c:14012:13: warning: the comparison will always evaluate as 'true' for the address of 'thread_sibling' will never be NULL [-Waddress]
> 14012 | if (!topology_sibling_cpumask(cpu)) {
> | ^
> In file included from include/linux/topology.h:30,
> from include/linux/gfp.h:8,
> from include/linux/xarray.h:16,
> from include/linux/list_lru.h:14,
> from include/linux/fs.h:13,
> from kernel/events/core.c:11:
> include/linux/arch_topology.h:78:19: note: 'thread_sibling' declared here
> 78 | cpumask_t thread_sibling;
> | ^~~~~~~~~~~~~~
>
> Introduced by commit
>
> 4ba4f1afb6a9 ("perf: Generic hotplug support for a PMU with a scope")
>
The patch to fix the warning has been posted.
https://lore.kernel.org/lkml/20240912145025.1574448-1-kan.liang@linux.intel.com/
Please give it a try.
Thanks,
Kan
Powered by blists - more mailing lists