lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250317160540.096f16a4@canb.auug.org.au>
Date: Mon, 17 Mar 2025 16:05:40 +1100
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: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Next
 Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the tip tree

Hi all,

On Tue, 11 Mar 2025 15:24:29 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> On Thu, 6 Mar 2025 15:25:16 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> >
> > On Tue, 4 Mar 2025 16:25:31 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:  
> > >
> > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
> > > failed like this:
> > > 
> > > In file included from include/asm-generic/percpu.h:7,
> > >                  from arch/x86/include/asm/percpu.h:597,
> > >                  from arch/x86/include/asm/preempt.h:6,
> > >                  from include/linux/preempt.h:79,
> > >                  from include/linux/spinlock.h:56,
> > >                  from include/linux/wait.h:9,
> > >                  from include/linux/wait_bit.h:8,
> > >                  from include/linux/fs.h:7,
> > >                  from kernel/events/core.c:11:
> > > kernel/events/core.c: In function 'this_cpc':
> > > include/linux/percpu-defs.h:220:45: error: initialization from pointer to non-enclosed address space
> > >   220 |         const void __percpu *__vpp_verify = (typeof((ptr) + 0))NULL;    \
> > >       |                                             ^
> > > include/linux/percpu-defs.h:251:9: note: in expansion of macro '__verify_pcpu_ptr'
> > >   251 |         __verify_pcpu_ptr(ptr);                                         \
> > >       |         ^~~~~~~~~~~~~~~~~
> > > kernel/events/core.c:1222:17: note: in expansion of macro 'this_cpu_ptr'
> > >  1222 |         return *this_cpu_ptr(pmu->cpu_pmu_context);
> > >       |                 ^~~~~~~~~~~~
> > > 
> > > (and many more similar)
> > > 
> > > Presumably caused by commit
> > > 
> > >   f67d1ffd841f ("perf/core: Detach 'struct perf_cpu_pmu_context' and 'struct pmu' lifetimes")
> > > 
> > > I have used the tip tree from next-20250303 for today.    
> > 
> > I am still seeing this build failure.  
> 
> Ditto.  Anything happening with this?
> 
> I am still using the tip tree from next-20250303.

So am I missing something here?  I am still seeing this build failure.

That commit is now

  4eabf533fb18 ("perf/core: Detach 'struct perf_cpu_pmu_context' and 'struct pmu' lifetimes")

Is there something in my toolchain?   Or some other difference in our
build environments?

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ