From: Peter Xu <peterx@redhat.com>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
"Huang, Ying" <ying.huang@intel.com>
Subject: Re: Cannot find symbol for section 69: .text.arch_max_swapfile_size.
Date: Mon, 14 Aug 2023 11:38:18 -0400 [thread overview]
Message-ID: <ZNpKaiweCbf9i5QS@x1n> (raw)
In-Reply-To: <202308120906.Efohswpa-lkp@intel.com>
On Sat, Aug 12, 2023 at 09:11:33AM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 190bf7b14b0cf3df19c059061be032bd8994a597
> commit: be45a4902c7caa717fee6b2f671e59b396ed395c mm/swap: cache maximum swapfile size when init swap
> date: 11 months ago
> config: mips-randconfig-r014-20230811 (https://download.01.org/0day-ci/archive/20230812/202308120906.Efohswpa-lkp@intel.com/config)
> compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git 4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a)
> reproduce: (https://download.01.org/0day-ci/archive/20230812/202308120906.Efohswpa-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/202308120906.Efohswpa-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> >> Cannot find symbol for section 69: .text.arch_max_swapfile_size.
> mm/swapfile.o: failed
Hmm.. I don't really know what's the issue here, neither can I reproduce
this locally - the cross build seems to all work with the reproducer and I
can see mm/swapfile.o correctly generated.
$ wget https://download.01.org/0day-ci/archive/20230812/202308120906.Efohswpa-lkp@intel.com/config
$ mv config .config
$ COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang ./make.cross W=1 O=build_dir ARCH=mips olddefconfig
[...]
$ COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang ./make.cross W=1 O=build_dir ARCH=mips SHELL=/bin/bash
[...]
FIT description: Linux 6.5.0-rc4-00492-gad3232df3e41
Created: Mon Aug 14 11:35:57 2023
Image 0 (kernel)
Description: Linux 6.5.0-rc4-00492-gad3232df3e41
Created: Mon Aug 14 11:35:57 2023
Type: Kernel Image
Compression: gzip compressed
Data Size: 1767982 Bytes = 1726.54 KiB = 1.69 MiB
Architecture: MIPS
OS: Linux
Load Address: 0x80100000
Entry Point: 0x8043e5f0
Hash algo: sha1
Hash value: 750e28c2fdd0d73eec9b0d8dbf5655579cb1364c
Default Configuration: 'conf-default'
Configuration 0 (conf-default)
Description: Generic Linux kernel
Kernel: kernel
$ file build_dir/mm/swapfile.o
build_dir/mm/swapfile.o: ELF 32-bit MSB relocatable, MIPS, MIPS32 version 1 (SYSV), not stripped
Please let me now if anyone knows what I'm missing.
--
Peter Xu
next prev parent reply other threads:[~2023-08-14 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 1:11 kernel test robot
2023-08-14 15:38 ` Peter Xu [this message]
2023-08-14 15:47 ` Nathan Chancellor
2023-08-15 1:49 ` Liu, Yujie
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=ZNpKaiweCbf9i5QS@x1n \
--to=peterx@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ying.huang@intel.com \
/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