From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Max Krummenacher <max.oss.09@gmail.com>
Cc: stable@vger.kernel.org, max.krummenacher@toradex.com
Subject: Re: regression on 6.1.129-rc with perf
Date: Tue, 18 Feb 2025 10:30:10 +0100 [thread overview]
Message-ID: <2025021843-confess-omit-42c6@gregkh> (raw)
In-Reply-To: <Z7NUbhkfDZeKeIu9@toolbox>
On Mon, Feb 17, 2025 at 04:23:26PM +0100, Max Krummenacher wrote:
> Our CI built linux-stable-rc.git queue/6.1 at commit eef4a8a45ba1
> ("btrfs: output the reason for open_ctree() failure").
> (built for arm and arm64, albeit I don't think it matters.)
>
> Building perf produced 2 build errors which I wanted to report
> even before the RC1 is out.
>
> | ...tools/perf/util/namespaces.c:247:27: error: invalid type argument of '->' (have 'int')
> | 247 | RC_CHK_ACCESS(nsi)->in_pidns = true;
> | | ^~
>
> introduced by commit 93520bacf784 ("perf namespaces: Introduce
> nsinfo__set_in_pidns()"). The RC_CK_ACCSS macro was introduced in 6.4.
> Removing the macro made this go away ( nsi->in_pidns = true; ).
>
>
> Second perf build error:
> | ld: ...tools/perf/util/machine.c:1176: undefined reference to `kallsyms__get_symbol_start'
>
> Introduced by commits:
> 710c2e913aa9 perf machine: Don't ignore _etext when not a text symbol
> 69a87a32f5cd perf machine: Include data symbols in the kernel map
>
> These two use the function kallsyms__get_symbol_start added with:
> f9dd531c5b82 perf symbols: Add kallsyms__get_symbol_start()
> So f9dd531c5b82 would additionally be needed.
>
>
> The kernel itself built fine, due to the perf error we don't have runtime
> testresults.
Thanks for letting me know, I'll go drop those patches from the queues
now. Dealing with perf issues on older kernels like this really isn't
needed.
thanks,
greg k-h
prev parent reply other threads:[~2025-02-18 9:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 15:23 regression on 6.1.129-rc with perf Max Krummenacher
2025-02-18 9:30 ` Greg Kroah-Hartman [this message]
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=2025021843-confess-omit-42c6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=max.krummenacher@toradex.com \
--cc=max.oss.09@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox