From: Thorsten Leemhuis <linux@leemhuis.info>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Cc: patches@lists.linux.dev, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
lkft-triage@lists.linaro.org, pavel@nabladev.com,
jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
sr@sladewatkins.com, Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH 7.3 0000/2651] 7.3.6-rc1 review
Date: Thu, 19 Nov 2026 08:03:14 +0100 [thread overview]
Message-ID: <b1aecdb0-5076-4df1-82a0-e4f5dc755578@leemhuis.info> (raw)
In-Reply-To: <f44f88e3-5d0c-4001-89d0-306d9d2aad04@leemhuis.info>
On 11/18/26 20:08, Thorsten Leemhuis wrote:
> On 11/18/26 15:20, Greg Kroah-Hartman wrote:
>> This is the start of the stable review cycle for the 7.3.6 release.
>> There are 2651 patches in this series, all will be posted as a response
>> to this one. If anyone has any issues with these being applied, please
>> let me know.
>>
>> Responses should be made by Fri, 20 Nov 2026 14:55:47 +0000.
>> Anything received after that time might be too late.
>>
>> The whole patch series can be found in one patch at:
>> https://www.kernel.org/pub/linux/kernel/v7.x/stable-review/patch-7.3.6-rc1.gz> [...]
>
> This failed to build for me on s390x while building tools/perf/:
> >> util/annotate-data.c: In function ‘global_var__collect’:
>> util/annotate-data.c:785:30: error: implicit declaration of function ‘die_get_type_die’; did you mean ‘die_get_typename’? [-Wimplicit-function-declaration]
>> 785 | if (!die_get_type_die(dwarf, pos->die_off, pos->die_tag,
>> | ^~~~~~~~~~~~~~~~
>> | die_get_typename
> [...]
By just following the hints in the error msg and a bit of searching on
lore I was able to fix this on 7.3.y-rc by cherry-picking 3dfdd195c7e45f
("perf dwarf-aux: Add die_same_file() and die_get_type_die()") [v7.4-rc1].
Then I ran into another error (see below), which I was able to fix by
cherry-picking fc076b5f4807a3 ("perf trace: Introduce kernel symbol
beautifier for virtual addresses") [v7.4-rc1]
Ciao, Thorsten
> builtin-trace.c: In function ‘trace__btf_scnprintf’:
> builtin-trace.c:1164:24: error: implicit declaration of function ‘syscall_arg__scnprintf_ksym’; did you mean ‘syscall_arg__scnprintf_buf’? [-Wimplicit-function-declaration]
> 1164 | return syscall_arg__scnprintf_ksym(bf, size, arg);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~
> | syscall_arg__scnprintf_buf
> make -f /[...]tools/build/Makefile.build dir=./util/annotate-arch obj=perf-util
> make -f /[...]tools/build/Makefile.build dir=./util/perf-regs-arch obj=perf-util
> make -f /[...]tools/build/Makefile.build dir=./util/kvm-stat-arch obj=perf-util
> make -f /[...]tools/build/Makefile.build dir=./util/intel-pt-decoder obj=perf-util
> make -f /[...]tools/build/Makefile.build dir=./util/arm-spe-decoder obj=perf-util
> make -f /[...]tools/build/Makefile.build dir=./util/hisi-ptt-decoder obj=perf-util
> make -f /[...]tools/build/Makefile.build dir=./util/dwarf-regs-arch obj=perf-util
> make -f /[...]tools/build/Makefile.build dir=./util/scripting-engines obj=perf-util
> builtin-trace.c: In function ‘syscall__scnprintf_args’:
> builtin-trace.c:2597:82: error: ‘SCA_KSYM’ undeclared (first use in this function)
> 2597 | default_scnprintf == SCA_PTR || default_scnprintf == SCA_KSYM) {
> | ^~~~~~~~
> builtin-trace.c:2597:82: note: each undeclared identifier is reported only once for each function it appears in
> make[3]: *** [/[...]tools/build/Makefile.build:96: /home/kbuilder/usr/tmp/out/builtin-trace.o] Error 1
> make[3]: *** Waiting for unfinished jobs....
> make[2]: *** [Makefile.perf:544: /home/kbuilder/usr/tmp/out/perf-in.o] Error 2
> make[2]: *** Waiting for unfinished jobs....
> make[1]: *** [Makefile.perf:283: sub-make] Error 2
> make: *** [Makefile:76: all] Error 2
> make: Leaving directory '/[...]tools/perf'
next prev parent reply other threads:[~2026-11-19 7:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 14:20 Greg Kroah-Hartman
2026-11-18 16:59 ` Brett A C Sheffield
2026-11-18 17:17 ` Pavel Machek
2026-11-18 19:02 ` Thorsten Leemhuis
2026-11-18 20:39 ` Gary Guo
2026-11-19 3:23 ` Alice C. Munduruca
2026-11-18 19:08 ` Thorsten Leemhuis
2026-11-19 7:03 ` Thorsten Leemhuis [this message]
2026-11-18 19:59 ` Florian Fainelli
2026-11-18 22:30 ` Takeshi Ogasawara
2026-11-19 3:32 ` Peter Schneider
2026-11-19 7:11 ` Joungmin Lee
2026-11-19 3:26 Sergey Lebedev
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=b1aecdb0-5076-4df1-82a0-e4f5dc755578@leemhuis.info \
--to=linux@leemhuis.info \
--cc=achill@achill.org \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=namhyung@kernel.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@nabladev.com \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=sr@sladewatkins.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®