linux-kernel - Re: linux-next: build failure after merge of the ftrace 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]

Date:   Fri, 14 Jan 2022 14:34:18 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Steven Rostedt <rostedt@...dmis.org>
Cc:     Yinan Liu <yinan@...ux.alibaba.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 ftrace tree

Hi Steve,

On Thu, 13 Jan 2022 22:25:39 -0500 Steven Rostedt <rostedt@...dmis.org> wrote:
>
> I can't reproduce it, and doing searches on this error, seems that it
> happens "randomly". I haven't found what can cause it yet.

rats :-(

> I don't have a way to build nativly, but if you send me your config, I
> can still try to cross compile it to see if it triggers.

I just use ppc64_defconfig (which may vary depending on what is merged
into my tree at the time).  I don't save actual .config files, sorry.

So:

$ make ARCH=powerpc ppc64_defconfig

> Does it fail on anything else?

This is the first build I do after merging each tree, so I don't know
about others.  I may be able to do some testing later today (after
linux-next is released).

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped