From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Chris Paterson <Chris.Paterson2@renesas.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: 4.14.321-rc1 build error
Date: Sun, 16 Jul 2023 16:36:23 +0200 [thread overview]
Message-ID: <2023071616-overture-flatbed-28e0@gregkh> (raw)
In-Reply-To: <TY2PR01MB37883616B104E56A1DDCA286B737A@TY2PR01MB3788.jpnprd01.prod.outlook.com>
On Thu, Jul 13, 2023 at 08:15:11AM +0000, Chris Paterson wrote:
> Hello Greg,
>
> I know you haven't formally released 4.14.321-rc1 for review yet, but our CI picked up a build issue so I thought I may as well report it in case it's useful information for you.
>
> SHA: Linux 4.14.321-rc1 (bc1094b21392)
> Failed build log: https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/jobs/4635722359
> defconfig used: https://gitlab.com/cip-project/cip-kernel/cip-kernel-config/-/blob/master/4.14.y/arm/moxa_mxc_defconfig
>
> Error log:
> /builds/cip-project/cip-testing/linux-stable-rc-ci/gcc/gcc-11.1.0-nolibc/arm-linux-gnueabi/bin/arm-linux-gnueabi-ld: arch/arm/probes/kprobes/core.o: in function `jprobe_return':
> /builds/cip-project/cip-testing/linux-stable-rc-ci/arch/arm/probes/kprobes/core.c:555: undefined reference to `kprobe_handler'
> Makefile:1049: recipe for target 'vmlinux' failed
> make: *** [vmlinux] Error 1
>
> Problem patch:
> Reverting 1c18f6ba04d8 ("ARM: 9303/1: kprobes: avoid missing-declaration warnings") makes the problem go away.
SHould now be fixed, thanks.
greg k-h
prev parent reply other threads:[~2023-07-16 14:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 8:15 4.14.321-rc1 build error Chris Paterson
2023-07-16 14:36 ` 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=2023071616-overture-flatbed-28e0@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Chris.Paterson2@renesas.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