linux-kernel - Re: linux-next: build failure after merge of the sysctl tree

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: <YkSoxQhTVitU6mh9@bombadil.infradead.org>
Date:   Wed, 30 Mar 2022 12:00:21 -0700
From:   Luis Chamberlain <mcgrof@...nel.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Wei Xiao <xiaowei66@...wei.com>,
        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 sysctl tree

On Wed, Mar 30, 2022 at 11:56:17AM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the sysctl tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
> 
> kernel/sysctl.c:1776:36: error: 'C_A_D' undeclared here (not in a function)
>  1776 |                 .data           = &C_A_D,
>       |                                    ^~~~~
> 
> Caused by commit
> 
>   84053cc7ef2f ("ftrace: move sysctl_ftrace_enabled to ftrace.c")
> 
> I can't imagine how that happened (though I do note that the whole branch
> has been rebased and not tested :-( ).

Sorry about that, indeed I rebased it and only test compiled the
conflicts.

> I have used the sysctl tree from next-20220329 for today.

I'll push to 0-day testing before pushing a new iteration.
Trying to prepare to push to Linus.

  Luis