[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240919082119.62324e11@canb.auug.org.au>
Date: Thu, 19 Sep 2024 08:21:19 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, Peter Zijlstra <peterz@...radead.org>
Cc: Kan Liang <kan.liang@...ux.intel.com>, 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
Hi all,
On Wed, 11 Sep 2024 15:38:54 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> 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")
This commit is now in Linus' tree and the warning is till there :-( In
fact this is a build failure for some configurations. A fix was
posted on Sep 13 (12?), please get it to Linus as soon as possible.
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists