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] [day] [month] [year] [list]

Message-ID: <20231025212126.689c6088@gandalf.local.home>
Date:   Wed, 25 Oct 2023 21:21:26 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Masami Hiramatsu <mhiramat@...nel.org>,
        "Matthew Wilcox (Oracle)" <willy@...radead.org>,
        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

On Thu, 26 Oct 2023 12:18:16 +1100
Stephen Rothwell <sfr@...b.auug.org.au> wrote:

> Hi all,
> 
> On Mon, 23 Oct 2023 13:30:33 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> > 
> > After merging the ftrace tree, today's linux-next build (powerpc
> > ppc64_defconfig) failed like this:
> > 
> > arch/powerpc/kernel/setup-common.c:604:10: error: 'struct seq_buf' has no member named 'readpos'
> >   604 |         .readpos = 0,
> >       |          ^~~~~~~
> > arch/powerpc/kernel/setup-common.c:604:20: error: excess elements in struct initializer [-Werror]
> >   604 |         .readpos = 0,
> >       |                    ^
> > arch/powerpc/kernel/setup-common.c:604:20: note: (near initialization for 'ppc_hw_desc')
> > cc1: all warnings being treated as errors
> > 
> > Caused by commit
> > 
> >   d0ed46b60396 ("tracing: Move readpos from seq_buf to trace_seq")
> > 
> > I have used the ftrace tree from next-20231020 for today.  
> 
> This is still failing ...
> 

Ah, I never pushed it up from trace/for-next to for-next. Thanks for the reminder.

I'll do that now.

-- Steve