Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Natanael Copa <ncopa@alpinelinux.org>
To: Greg Thelen <gthelen@google.com>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>, Greg KH <greg@kroah.com>,
	Viktor Malik <vmalik@redhat.com>,
	Andrii Nakryiko <andrii@kernel.org>, Daniel Xu <dxu@dxuuu.xyz>,
	Alexei Starovoitov <ast@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>,
	Linux Stable <stable@vger.kernel.org>
Subject: Re: stable kernels 6.6.23 and 6.1.83 fails to build: error: unknown type name 'u32'
Date: Mon, 1 Apr 2024 17:27:27 +0200	[thread overview]
Message-ID: <20240401172727.08b65053@ncopa-desktop.lan> (raw)
In-Reply-To: <CAHH2K0apZttqAhMZ9H_fygUC_Oa9G5-4XYmmqZu-EWNOuqc4Xg@mail.gmail.com>

On Mon, 1 Apr 2024 07:36:08 -0700
Greg Thelen <gthelen@google.com> wrote:

> On Mon, Apr 1, 2024 at 7:26*AM Bagas Sanjaya <bagasdotme@gmail.com> wrote:
> >
> > On Mon, Apr 01, 2024 at 04:15:25PM +0200, Greg KH wrote:  
> > > On Mon, Apr 01, 2024 at 09:09:55PM +0700, Bagas Sanjaya wrote:  
> > > > Hi,
> > > >
> > > > On Bugzilla, ncopa@alpinelinux.org reported resolve_btfids FTBFS regression
> > > > on musl system [1]:
> > > >  
> > > > > The latest releases fails to build with musl libc (Alpine Linux edge and v3.19):
> > > > >
> > > > > ```
> > > > > rm -f -f /home/ncopa/aports/main/linux-lts/src/build-lts.x86_64/tools/bpf/resolve_btfids/libbpf/libbpf.a; ar rcs /home/ncopa/aports/main/linux-lts/src/build-lts.x86_64/tool
> > > > > s/bpf/resolve_btfids/libbpf/libbpf.a /home/ncopa/aports/main/linux-lts/src/build-lts.x86_64/tools/bpf/resolve_btfids/libbpf/staticobjs/libbpf-in.o
> > > > > In file included from main.c:73:
> > > > > /home/ncopa/aports/main/linux-lts/src/linux-6.6/tools/include/linux/btf_ids.h:7:9: error: unknown type name 'u32'
> > > > >     7 |         u32 cnt;
> > > > >       |         ^~~
> > > > > /home/ncopa/aports/main/linux-lts/src/linux-6.6/tools/include/linux/btf_ids.h:8:9: error: unknown type name 'u32'
> > > > >     8 |         u32 ids[];
> > > > >       |         ^~~
> > > > > /home/ncopa/aports/main/linux-lts/src/linux-6.6/tools/include/linux/btf_ids.h:12:9: error: unknown type name 'u32'
> > > > >    12 |         u32 cnt;
> > > > >       |         ^~~
> > > > > /home/ncopa/aports/main/linux-lts/src/linux-6.6/tools/include/linux/btf_ids.h:13:9: error: unknown type name 'u32'
> > > > >    13 |         u32 flags;
> > > > >       |         ^~~
> > > > > /home/ncopa/aports/main/linux-lts/src/linux-6.6/tools/include/linux/btf_ids.h:15:17: error: unknown type name 'u32'
> > > > >    15 |                 u32 id;
> > > > >       |                 ^~~
> > > > > /home/ncopa/aports/main/linux-lts/src/linux-6.6/tools/include/linux/btf_ids.h:16:17: error: unknown type name 'u32'
> > > > >    16 |                 u32 flags;
> > > > >       |                 ^~~
> > > > > /home/ncopa/aports/main/linux-lts/src/linux-6.6/tools/include/linux/btf_ids.h:215:8: error: unknown type name 'u32'
> > > > >   215 | extern u32 btf_tracing_ids[];
> > > > >       |        ^~~
> > > > > make[4]: *** [/home/ncopa/aports/main/linux-lts/src/linux-6.6/tools/build/Makefile.build:98: /home/ncopa/aports/main/linux-lts/src/build-lts.x86_64/tools/bpf/resolve_btfids
> > > > > /main.o] Error 1
> > > > > make[4]: *** Waiting for unfinished jobs....
> > > > > make[3]: *** [Makefile:83: /home/ncopa/aports/main/linux-lts/src/build-lts.x86_64/tools/bpf/resolve_btfids//resolve_btfids-in.o] Error 2
> > > > > make[2]: *** [Makefile:76: bpf/resolve_btfids] Error 2
> > > > > make[1]: *** [/home/ncopa/aports/main/linux-lts/src/linux-6.6/Makefile:1354: tools/bpf/resolve_btfids] Error 2
> > > > > make: *** [/home/ncopa/aports/main/linux-lts/src/linux-6.6/Makefile:234: __sub-make] Error 2
> > > > > ```  
> > > >
> > > > Bisection led to upstream commit 9707ac4fe2f5ba ("tools/resolve_btfids:
> > > > Refactor set sorting with types from btf_ids.h") as the culprit.
> > > >
> > > > See the report on Bugzilla for the full thread and proposed fix.  
> > >
> > > Is the proposed fix a commit to backport?  
> >
> > Nope (see below).
> >  
> > >
> > > Digging through entries is not the easiest way to get things resolved...
> > >  
> >
> > The reporter posted the fix as bug comment [1] instead (hint: include
> > linux/types.h) but not submitted it to mailing lists first.
> >
> > Thanks.
> >
> > [1]: https://bugzilla.kernel.org/show_bug.cgi?id=218647#c2
> >
> > --
> > An old man doll... just what I always wanted! - Clara  
> 
> Does https://lore.kernel.org/all/20240328110103.28734-1-ncopa@alpinelinux.org/
> resolve this? It's staged in the bpf tree. Though I'm not sure when
> it'll be merged upstream.

Yes. this is the fix

-nc

  reply	other threads:[~2024-04-01 15:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-01 14:09 Fwd: stable kernels 6.6.23 and 6.1.83 fails to build: error: unknown type name 'u32' Bagas Sanjaya
2024-04-01 14:15 ` Greg KH
2024-04-01 14:26   ` Bagas Sanjaya
2024-04-01 14:36     ` Greg Thelen
2024-04-01 15:27       ` Natanael Copa [this message]
2024-04-01 15:09     ` Alexei Starovoitov
2024-04-01 15:24       ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240401172727.08b65053@ncopa-desktop.lan \
    --to=ncopa@alpinelinux.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bagasdotme@gmail.com \
    --cc=dxu@dxuuu.xyz \
    --cc=greg@kroah.com \
    --cc=gthelen@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=vmalik@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox