linux-kernel - Re: linux-next: Tree for Jul 14

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]

Date:   Thu, 14 Jul 2022 09:05:43 -0700
From:   Nathan Chancellor <nathan@...nel.org>
To:     "Sudip Mukherjee (Codethink)" <sudipm.mukherjee@...il.com>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        llvm@...ts.linux.dev
Subject: Re: linux-next: Tree for Jul 14

Hi Sudip,

On Thu, Jul 14, 2022 at 12:07:06PM +0100, Sudip Mukherjee (Codethink) wrote:
> Hi Stephen,
> 
> On Thu, Jul 14, 2022 at 06:55:14PM +1000, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Changes since 20220713:
> 
> Build failures on next-20220714:

<snip>

> x86_64 allmodconfig with clang fails with:
> 
> drivers/clk/qcom/gpucc-sm8350.c:111:2: error: initializer element is not a compile-time constant
>         gpu_cc_parent,
>         ^~~~~~~~~~~~~
> drivers/clk/qcom/gpucc-sm8350.c:126:2: error: initializer element is not a compile-time constant
>         gpu_cc_parent,
>         ^~~~~~~~~~~~~

I sent https://lore.kernel.org/20220711174004.3047516-1-nathan@kernel.org/
for this a few days ago, it just needs to be picked up.

> arch/x86/kernel/cpu/bugs.c:58:21: error: section attribute is specified on redeclared variable [-Werror,-Wsection]
> DEFINE_PER_CPU(u64, x86_spec_ctrl_current);
>                     ^
> ./arch/x86/include/asm/nospec-branch.h:283:12: note: previous declaration is here
> extern u64 x86_spec_ctrl_current;

This is now fixed in -tip so it should be fixed in -next tomorrorow:

https://git.kernel.org/tip/db866d3352ec85e821e730e191481cba3a2bfa6e

In the future, consider CC'ing our mailing list (llvm@...ts.linux.dev)
for any clang related issues so that we can get them taken care of ASAP,
we have a MAINTAINERS entry for a reason :) thank you for testing with
clang; the more people that use it, hopefully the easier it will be to
get things unbroken.

Cheers,
Nathan