From: Francis Laniel <flaniel@linux.microsoft.com>
To: "Daniel Díaz" <daniel.diaz@linaro.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, allen.lkml@gmail.com,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH 5.15 00/69] 5.15.141-rc1 review
Date: Fri, 01 Dec 2023 10:35:33 +0100 [thread overview]
Message-ID: <4879383.31r3eYUQgx@pwmachine> (raw)
In-Reply-To: <2023120134-sabotage-handset-0b0d@gregkh>
Hi!
Le vendredi 1 décembre 2023, 09:21:33 CET Greg Kroah-Hartman a écrit :
> On Thu, Nov 30, 2023 at 12:11:31PM -0600, Daniel Díaz wrote:
> > Hello!
> >
> > On Thu, 30 Nov 2023 at 11:44, Guenter Roeck <linux@roeck-us.net> wrote:
> > > On 11/30/23 09:21, Daniel Díaz wrote:
> > > > Hello!
> > > >
> > > > Lots of failures everywhere:
> > > > * clang-17-lkftconfig arm64
> > > > * clang-17-lkftconfig arm64
> > > > * clang-17-lkftconfig arm64
> > > > * clang-lkftconfig arm64
> > > > * clang-lkftconfig arm
> > > > * clang-lkftconfig i386
> > > > * clang-lkftconfig x86_64
> > > > * gcc-12-lkftconfig arm64
> > > > * gcc-12-lkftconfig arm
> > > > * gcc-12-lkftconfig i386
> > > > * gcc-12-lkftconfig x86_64
> > > > * gcc-12-lkftconfig-64k_page_size arm64
> > > > * gcc-12-lkftconfig-64k_page_size arm64
> > > > * gcc-12-lkftconfig-armv8_features arm64
> > > > * gcc-12-lkftconfig-debug arm64
> > > > * gcc-12-lkftconfig-debug arm64
> > > > * gcc-12-lkftconfig-debug arm
> > > > * gcc-12-lkftconfig-debug i386
> > > > * gcc-12-lkftconfig-debug x86_64
> > > > * gcc-12-lkftconfig-debug-kmemleak arm64
> > > > * gcc-12-lkftconfig-debug-kmemleak arm
> > > > * gcc-12-lkftconfig-debug-kmemleak i386
> > > > * gcc-12-lkftconfig-debug-kmemleak x86_64
> > > > * gcc-12-lkftconfig-devicetree arm64
> > > > * gcc-12-lkftconfig-kasan arm64
> > > > * gcc-12-lkftconfig-kasan arm64
> > > > * gcc-12-lkftconfig-kasan x86_64
> > > > * gcc-12-lkftconfig-kselftest arm64
> > > > * gcc-12-lkftconfig-kselftest-kernel arm64
> > > > * gcc-12-lkftconfig-kselftest-kernel arm
> > > > * gcc-12-lkftconfig-kselftest-kernel i386
> > > > * gcc-12-lkftconfig-kunit arm64
> > > > * gcc-12-lkftconfig-kunit arm64
> > > > * gcc-12-lkftconfig-kunit arm
> > > > * gcc-12-lkftconfig-kunit i386
> > > > * gcc-12-lkftconfig-kunit x86_64
> > > > * gcc-12-lkftconfig-libgpiod arm64
> > > > * gcc-12-lkftconfig-libgpiod arm
> > > > * gcc-12-lkftconfig-libgpiod i386
> > > > * gcc-12-lkftconfig-libgpiod x86_64
> > > > * gcc-12-lkftconfig-perf arm64
> > > > * gcc-12-lkftconfig-perf-kernel arm64
> > > > * gcc-12-lkftconfig-perf-kernel arm
> > > > * gcc-12-lkftconfig-perf-kernel i386
> > > > * gcc-12-lkftconfig-perf-kernel x86_64
> > > > * gcc-12-lkftconfig-rcutorture arm64
> > > > * gcc-12-lkftconfig-rcutorture arm64
> > > > * gcc-12-lkftconfig-rcutorture arm
> > > > * gcc-12-lkftconfig-rcutorture i386
> > > > * gcc-12-lkftconfig-rcutorture x86_64
> > > >
> > > > It's essentially this:
> > > >
> > > > -----8<-----
> > > >
> > > > make --silent --keep-going --jobs=8
> > > >
> > > > O=/home/tuxbuild/.cache/tuxmake/builds/1/build ARCH=x86_64 SRCARCH=x86
> > > > CROSS_COMPILE=x86_64-linux-gnu- 'CC=sccache x86_64-linux-gnu-gcc'
> > > > 'HOSTCC=sccache gcc'
> > > >
> > > > arch/x86/kernel/smp.o: warning: objtool: sysvec_reboot()+0x51:
> > > > unreachable instruction
> > > >
> > > > x86_64-linux-gnu-ld: kernel/trace/trace_kprobe.o: in function
> > > >
> > > > `__trace_kprobe_create':
> > > > trace_kprobe.c:(.text+0x2f39): undefined reference to
> > > >
> > > > `kallsyms_on_each_symbol'
> > > >
> > > > x86_64-linux-gnu-ld: kernel/trace/trace_kprobe.o: in function
> > > >
> > > > `create_local_trace_kprobe':
> > > > trace_kprobe.c:(.text+0x384b): undefined reference to
> > > >
> > > > `kallsyms_on_each_symbol'
> > > >
> > > > make[1]: *** [/builds/linux/Makefile:1227: vmlinux] Error 1
> > > > make[1]: Target '__all' not remade because of errors.
> > > > make: *** [Makefile:226: __sub-make] Error 2
> > > > make: Target '__all' not remade because of errors.
> > > >
> > > > ----->8-----
> > > >
> > > > It only affects 5.15. Bisection in progress.
> > >
> > > I guess it will point to
> > >
> > > >> Francis Laniel <flaniel@linux.microsoft.com>
> > > >>
> > > >> tracing/kprobes: Return EADDRNOTAVAIL when func matches several
> > > >> symbols
> >
> > It sure did!:
> > commit 7b4375c36a4c0e1b4b97ccbcdd427db5a460e04f
> > Author: Francis Laniel <flaniel@linux.microsoft.com>
> > Date: Fri Oct 20 13:42:49 2023 +0300
> >
> > tracing/kprobes: Return EADDRNOTAVAIL when func matches several
> > symbols
> >
> > commit b022f0c7e404887a7c5229788fc99eff9f9a80d5 upstream.
> >
> > Reverting that commit made the build pass again.
>
> {sigh}
>
> Francis, I think this is the second or third time this has happened with
> the attempt to get this patch merged. I'm going to go drop it from all
> of the pending stable queues again, and please, if you wish to have it
> applied in the future, I am going to have to see some proof it was
> actually tested on the architectures that it keeps breaking.
Sorry for the disagreement, for this one, I had to add the CONFIG_LIVEPATCH to
then be able to call kallsyms_on_each_symbol(), as on 5.15, this function is
within a ifdef guard [1].
I suppose you do not want to add CONFIG_LIVEPATCH to default config, so I will
try to find a way for this specific kernel!
Did you get problems only for 5.15 kernel? Or others too?
In the second case, can you please link me the problems and I will polish
everything.
> thanks,
>
> greg k-h
Best regards.
---
[1]: https://elixir.bootlin.com/linux/v5.15.140/source/kernel/kallsyms.c#L207
next prev parent reply other threads:[~2023-12-01 9:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 16:21 [PATCH 5.15 00/69] 5.15.141-rc1 review Greg Kroah-Hartman
2023-11-30 17:21 ` Daniel Díaz
2023-11-30 17:44 ` Guenter Roeck
2023-11-30 18:11 ` Daniel Díaz
2023-11-30 18:56 ` Guenter Roeck
2023-12-01 8:21 ` Greg Kroah-Hartman
2023-12-01 9:35 ` Francis Laniel [this message]
2023-12-01 9:44 ` Greg Kroah-Hartman
2023-12-01 14:34 ` Daniel Díaz
2023-12-01 23:04 ` Greg Kroah-Hartman
2023-12-04 14:55 ` Daniel Díaz
2023-12-01 6:31 ` Harshit Mogalapalli
2023-11-30 22:27 ` Pavel Machek
2023-11-30 18:57 ` Florian Fainelli
2023-12-01 0:08 ` Shuah Khan
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=4879383.31r3eYUQgx@pwmachine \
--to=flaniel@linux.microsoft.com \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=conor@kernel.org \
--cc=daniel.diaz@linaro.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--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