From: Baoquan He <bhe@redhat.com>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [linux-next:master 1576/1892] s390-linux-ld: drivers/of/kexec.c:399:undefined reference to `crashk_res'
Date: Mon, 29 Jan 2024 22:43:50 +0800 [thread overview]
Message-ID: <Zbe5pszGN9AgBOgM@MiWiFi-R3L-srv> (raw)
In-Reply-To: <202401291400.2iU26ixw-lkp@intel.com>
On 01/29/24 at 02:37pm, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 596764183be8ebb13352b281a442a1f1151c9b06
> commit: ad82e944d12ca472df041acb4c732bd630a81b90 [1576/1892] s390, crash: wrap crash dumping code into crash related ifdefs
> config: s390-randconfig-r023-20230616 (https://download.01.org/0day-ci/archive/20240129/202401291400.2iU26ixw-lkp@intel.com/config)
> compiler: s390-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240129/202401291400.2iU26ixw-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202401291400.2iU26ixw-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> s390-linux-ld: arch/s390/kernel/machine_kexec.o: in function `arch_crash_save_vmcoreinfo':
> arch/s390/kernel/machine_kexec.c:216:(.text+0x1c0): undefined reference to `vmcoreinfo_append_str'
> s390-linux-ld: arch/s390/kernel/machine_kexec.c:217:(.text+0x1d8): undefined reference to `vmcoreinfo_append_str'
> s390-linux-ld: arch/s390/kernel/machine_kexec.c:218:(.text+0x1ee): undefined reference to `vmcoreinfo_append_str'
> s390-linux-ld: arch/s390/kernel/machine_kexec.c:219:(.text+0x206): undefined reference to `vmcoreinfo_append_str'
> s390-linux-ld: arch/s390/kernel/machine_kexec.c:220:(.text+0x21e): undefined reference to `vmcoreinfo_append_str'
> s390-linux-ld: arch/s390/kernel/machine_kexec.o:arch/s390/kernel/machine_kexec.c:221: more undefined references to `vmcoreinfo_append_str' follow
> s390-linux-ld: arch/s390/kernel/machine_kexec.o: in function `arch_crash_save_vmcoreinfo':
> arch/s390/kernel/machine_kexec.c:223:(.text+0x254): undefined reference to `paddr_vmcoreinfo_note'
Thanks for reporting these. These errors has been reported by Nathan.
Above error is fixed in below patch:
[PATCH linux-next 3/3] arch, crash: move arch_crash_save_vmcoreinfo() out to file vmcore_info.c
https://lore.kernel.org/all/20240129135033.157195-3-bhe@redhat.com/T/#u
> s390-linux-ld: drivers/of/kexec.o: in function `of_kexec_alloc_and_setup_fdt':
> drivers/of/kexec.c:399:(.text+0x922): undefined reference to `crashk_res'
> >> s390-linux-ld: drivers/of/kexec.c:399:(.text+0x944): undefined reference to `crashk_res'
> s390-linux-ld: drivers/of/kexec.c:401:(.text+0x970): undefined reference to `crashk_res'
> s390-linux-ld: drivers/of/kexec.c:405:(.text+0x9aa): undefined reference to `crashk_low_res'
> s390-linux-ld: drivers/of/kexec.c:405:(.text+0x9d0): undefined reference to `crashk_low_res'
> s390-linux-ld: drivers/of/kexec.c:406:(.text+0x9fc): undefined reference to `crashk_low_res'
Above error is fixed in
[PATCH linux-next 2/3] crash: fix building error in generic codes
https://lore.kernel.org/all/20240129135033.157195-2-bhe@redhat.com/T/#u
prev parent reply other threads:[~2024-01-29 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 6:37 [linux-next:master 1576/1892] s390-linux-ld: drivers/of/kexec.c:399:undefined reference to `crashk_res' kernel test robot
2024-01-29 14:43 ` Baoquan He [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=Zbe5pszGN9AgBOgM@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).