All of lore.kernel.org
 help / color / mirror / Atom feed
From: Natanael Copa <ncopa@alpinelinux.org>
To: "Sergio González Collado" <sergio.collado@gmail.com>
Cc: stable@vger.kernel.org, regressions@lists.linux.dev,
	Achill Gilgenast <fossdd@pwned.life>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [REGRESSION] v6.12.35: (build) kallsyms.h:21:10: fatal error: execinfo.h: No such file or directory
Date: Wed, 2 Jul 2025 12:42:47 +0200	[thread overview]
Message-ID: <20250702124247.7540ec3a@ncopa-desktop> (raw)
In-Reply-To: <CAA76j90io241-a+2SDLfAMHY2ro4x-Bstw4AxKDOU_izW9goYg@mail.gmail.com>

On Tue, 1 Jul 2025 19:07:32 +0200
Sergio González Collado <sergio.collado@gmail.com> wrote:

> Hello,

Hi Sergio,

>  Thanks for pointing that out. I was not aware of it.

No worries. It happens. Just slightly unfortunate that it tickled down
to stable branches before it got fixed.

It is trivial to fix but I wonder what is the best way though. Achill
proposed to use #ifdef HAVE_BACKTRACE_SUPPORT in
tools/include/linux/kallsyms.h but it appears that this was included
only for KSYM_NAME_LEN.

KSYM_NAME_LEN appears to be defined multiple places:

$ rg 'KSYM_NAME_LEN\s+512'
include/linux/kallsyms.h
18:#define KSYM_NAME_LEN 512

tools/include/linux/kallsyms.h
9:#define KSYM_NAME_LEN 512

tools/lib/perf/include/perf/event.h
107:#define KSYM_NAME_LEN 512

tools/lib/symbol/kallsyms.h
10:#define KSYM_NAME_LEN 512

scripts/kallsyms.c
34:#define KSYM_NAME_LEN                512

So I wonder if it would be acceptable to simply:

diff --git a/arch/x86/tools/insn_decoder_test.c b/arch/x86/tools/insn_decoder_test.c
index 08cd913cbd4e..7916bf487ed2 100644
--- a/arch/x86/tools/insn_decoder_test.c
+++ b/arch/x86/tools/insn_decoder_test.c
@@ -10,7 +10,6 @@
 #include <assert.h>
 #include <unistd.h>
 #include <stdarg.h>
-#include <linux/kallsyms.h>
 
 #include <asm/insn.h>
 #include <inat.c>
@@ -105,6 +104,7 @@ static void parse_args(int argc, char **argv)
        }
 }
 
+#define KSYM_NAME_LEN 512
 #define BUFSIZE (256 + KSYM_NAME_LEN)
 
 int main(int argc, char **argv)

I am also confused with who should be in the CC list.

Thanks!
-nc
 
> On Tue, 1 Jul 2025 at 14:10, Natanael Copa <ncopa@alpinelinux.org> wrote:
> >
> > Hi!
> >
> > I bumped into a build regression when building Alpine Linux kernel 6.12.35 on x86_64:
> >
> > In file included from ../arch/x86/tools/insn_decoder_test.c:13:
> > ../tools/include/linux/kallsyms.h:21:10: fatal error: execinfo.h: No such file or directory
> >    21 | #include <execinfo.h>
> >       |          ^~~~~~~~~~~~
> > compilation terminated.
> >
> > The 6.12.34 kernel built just fine.
> >
> > I bisected it to:
> >
> > commit b8abcba6e4aec53868dfe44f97270fc4dee0df2a (HEAD)
> > Author: Sergio Gonz_lez Collado <sergio.collado@gmail.com>
> > Date:   Sun Mar 2 23:15:18 2025 +0100
> >
> >     Kunit to check the longest symbol length
> >
> >     commit c104c16073b7fdb3e4eae18f66f4009f6b073d6f upstream.
> >
> > which has this hunk:
> >
> > diff --git a/arch/x86/tools/insn_decoder_test.c b/arch/x86/tools/insn_decoder_test.c
> > index 472540aeabc2..6c2986d2ad11 100644
> > --- a/arch/x86/tools/insn_decoder_test.c
> > +++ b/arch/x86/tools/insn_decoder_test.c
> > @@ -10,6 +10,7 @@
> >  #include <assert.h>
> >  #include <unistd.h>
> >  #include <stdarg.h>
> > +#include <linux/kallsyms.h> 
> >
> >  #define unlikely(cond) (cond)
> >
> > @@ -106,7 +107,7 @@ static void parse_args(int argc, char **argv)
> >         }
> >  }
> >
> > -#define BUFSIZE 256
> > +#define BUFSIZE (256 + KSYM_NAME_LEN)
> >
> >  int main(int argc, char **argv)
> >  {
> >
> > It looks like the linux/kallsyms.h was included to get
> > KSYM_NAME_LEN. Unfortunately it also introduced the include of
> > execinfo.h, which does not exist on musl libc.
> >
> > This has previously been reported to and tried fixed:
> > https://lore.kernel.org/stable/DB0OSTC6N4TL.2NK75K2CWE9JV@pwned.life/T/#t
> >
> > Would it be an idea to revert commit b8abcba6e4ae til we have a
> > proper solution for this?
> >
> > Thanks!
> >
> > -nc  


  reply	other threads:[~2025-07-02 10:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-01 12:10 [REGRESSION] v6.12.35: (build) kallsyms.h:21:10: fatal error: execinfo.h: No such file or directory Natanael Copa
2025-07-01 12:26 ` Greg Kroah-Hartman
2025-07-13 14:27   ` Achill Gilgenast
2025-07-13 14:38     ` Greg Kroah-Hartman
2025-07-13 15:11       ` Achill Gilgenast
2025-07-01 17:07 ` Sergio González Collado
2025-07-02 10:42   ` Natanael Copa [this message]
2025-07-02 11:06     ` Achill Gilgenast

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=20250702124247.7540ec3a@ncopa-desktop \
    --to=ncopa@alpinelinux.org \
    --cc=fossdd@pwned.life \
    --cc=gregkh@linuxfoundation.org \
    --cc=regressions@lists.linux.dev \
    --cc=sergio.collado@gmail.com \
    --cc=stable@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.