From: kernel test robot <lkp@intel.com>
To: Maxwell Bland <mbland@motorola.com>, linux-mm@kvack.org
Cc: oe-kbuild-all@lists.linux.dev,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Zi Shen Lim <zlim.lnx@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Uladzislau Rezki <urezki@gmail.com>,
Christoph Hellwig <hch@infradead.org>,
Lorenzo Stoakes <lstoakes@gmail.com>,
Mark Rutland <mark.rutland@arm.com>,
Ard Biesheuvel <ardb@kernel.org>,
Maxwell Bland <mbland@motorola.com>,
Russell King <linux@armlinux.org.uk>,
Masami Hiramatsu <mhiramat@kernel.org>,
Shaoqin Huang <shahuang@redhat.com>,
Ryo Takakura <takakura@valinux.co.jp>,
James Morse <james.morse@arm.com>,
Ryan Roberts <ryan.roberts@arm.com>
Subject: Re: [PATCH v5 1/2] mm: allow dynamic vmalloc range restrictions
Date: Sat, 11 May 2024 13:30:01 +0800 [thread overview]
Message-ID: <202405111325.7IRuG4ZE-lkp@intel.com> (raw)
In-Reply-To: <ozcyvkcdqhxhlg3sjz3s4odt7ejiwx2cctgb7sdx6jbardui37@al6uvt4yx5nt>
Hi Maxwell,
kernel test robot noticed the following build errors:
[auto build test ERROR on ee5b455b0adae9ecafb38b174c648c48f2a3c1a5]
url: https://github.com/intel-lab-lkp/linux/commits/Maxwell-Bland/arm64-mm-code-and-data-allocation-partitioning/20240510-022822
base: ee5b455b0adae9ecafb38b174c648c48f2a3c1a5
patch link: https://lore.kernel.org/r/ozcyvkcdqhxhlg3sjz3s4odt7ejiwx2cctgb7sdx6jbardui37%40al6uvt4yx5nt
patch subject: [PATCH v5 1/2] mm: allow dynamic vmalloc range restrictions
config: openrisc-defconfig (https://download.01.org/0day-ci/archive/20240511/202405111325.7IRuG4ZE-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240511/202405111325.7IRuG4ZE-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/202405111325.7IRuG4ZE-lkp@intel.com/
All errors (new ones prefixed by >>):
or1k-linux-ld: init/do_mounts.o: in function `arch_init_checked_vmap_ranges':
>> do_mounts.c:(.init.text+0x53c): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: init/do_mounts_initrd.o: in function `arch_init_checked_vmap_ranges':
do_mounts_initrd.c:(.init.text+0x100): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: init/initramfs.o: in function `arch_init_checked_vmap_ranges':
initramfs.c:(.init.text+0x13b4): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: init/init_task.o: in function `arch_init_checked_vmap_ranges':
init_task.c:(.init.text+0x0): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: arch/openrisc/kernel/setup.o: in function `arch_init_checked_vmap_ranges':
setup.c:(.init.text+0x6c): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: arch/openrisc/kernel/or32_ksyms.o: in function `arch_init_checked_vmap_ranges':
or32_ksyms.c:(.init.text+0x0): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: arch/openrisc/kernel/process.o: in function `arch_init_checked_vmap_ranges':
process.c:(.init.text+0x0): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: arch/openrisc/kernel/dma.o: in function `arch_init_checked_vmap_ranges':
dma.c:(.init.text+0x0): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: arch/openrisc/kernel/traps.o: in function `arch_init_checked_vmap_ranges':
traps.c:(.init.text+0x0): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: arch/openrisc/kernel/time.o: in function `arch_init_checked_vmap_ranges':
time.c:(.init.text+0x0): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: arch/openrisc/kernel/irq.o: in function `arch_init_checked_vmap_ranges':
irq.c:(.init.text+0x0): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: arch/openrisc/kernel/signal.o: in function `arch_init_checked_vmap_ranges':
signal.c:(.init.text+0x0): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: arch/openrisc/kernel/sys_call_table.o: in function `arch_init_checked_vmap_ranges':
sys_call_table.c:(.init.text+0x0): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: arch/openrisc/mm/fault.o: in function `arch_init_checked_vmap_ranges':
fault.c:(.init.text+0x0): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: arch/openrisc/mm/init.o: in function `arch_init_checked_vmap_ranges':
init.c:(.init.text+0x21c): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: arch/openrisc/mm/ioremap.o: in function `arch_init_checked_vmap_ranges':
ioremap.c:(.init.text+0x0): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/fork.o: in function `arch_init_checked_vmap_ranges':
fork.c:(.init.text+0x40): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/exec_domain.o: in function `arch_init_checked_vmap_ranges':
exec_domain.c:(.init.text+0x44): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/panic.o: in function `arch_init_checked_vmap_ranges':
panic.c:(.init.text+0x204): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/cpu.o: in function `arch_init_checked_vmap_ranges':
cpu.c:(.init.text+0xb0): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/exit.o: in function `arch_init_checked_vmap_ranges':
exit.c:(.init.text+0x84): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/softirq.o: in function `arch_init_checked_vmap_ranges':
softirq.c:(.init.text+0x8c): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/resource.o: in function `arch_init_checked_vmap_ranges':
resource.c:(.init.text+0x2dc): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/sysctl.o: in function `arch_init_checked_vmap_ranges':
sysctl.c:(.init.text+0x0): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/capability.o: in function `arch_init_checked_vmap_ranges':
capability.c:(.init.text+0x2c): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/ptrace.o: in function `arch_init_checked_vmap_ranges':
ptrace.c:(.init.text+0x0): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/user.o: in function `arch_init_checked_vmap_ranges':
user.c:(.init.text+0xb0): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/signal.o: in function `arch_init_checked_vmap_ranges':
signal.c:(.init.text+0x84): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/sys.o: in function `arch_init_checked_vmap_ranges':
sys.c:(.init.text+0x0): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/umh.o: in function `arch_init_checked_vmap_ranges':
umh.c:(.init.text+0x48): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/workqueue.o: in function `arch_init_checked_vmap_ranges':
workqueue.c:(.init.text+0x7e8): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/pid.o: in function `arch_init_checked_vmap_ranges':
pid.c:(.init.text+0x0): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/task_work.o: in function `arch_init_checked_vmap_ranges':
task_work.c:(.init.text+0x0): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/extable.o: in function `arch_init_checked_vmap_ranges':
extable.c:(.init.text+0x0): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/params.o: in function `arch_init_checked_vmap_ranges':
params.c:(.init.text+0x444): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/kthread.o: in function `arch_init_checked_vmap_ranges':
kthread.c:(.init.text+0x0): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/nsproxy.o: in function `arch_init_checked_vmap_ranges':
nsproxy.c:(.init.text+0x48): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/notifier.o: in function `arch_init_checked_vmap_ranges':
notifier.c:(.init.text+0x0): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/ksysfs.o: in function `arch_init_checked_vmap_ranges':
ksysfs.c:(.init.text+0xe0): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/cred.o: in function `arch_init_checked_vmap_ranges':
cred.c:(.init.text+0x44): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/reboot.o: in function `arch_init_checked_vmap_ranges':
reboot.c:(.init.text+0x2c0): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/ucount.o: in function `arch_init_checked_vmap_ranges':
ucount.c:(.init.text+0x0): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/ksyms_common.o: in function `arch_init_checked_vmap_ranges':
ksyms_common.c:(.init.text+0x0): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/groups.o: in function `arch_init_checked_vmap_ranges':
groups.c:(.init.text+0x0): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/sched/core.o: in function `arch_init_checked_vmap_ranges':
core.c:(.init.text+0x44): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/sched/fair.o: in function `arch_init_checked_vmap_ranges':
fair.c:(.init.text+0xbc): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/sched/build_policy.o: in function `arch_init_checked_vmap_ranges':
build_policy.c:(.init.text+0x90): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/sched/build_utility.o: in function `arch_init_checked_vmap_ranges':
build_utility.c:(.init.text+0x44): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/locking/mutex.o: in function `arch_init_checked_vmap_ranges':
mutex.c:(.init.text+0x0): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/locking/semaphore.o: in function `arch_init_checked_vmap_ranges':
semaphore.c:(.init.text+0x0): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
or1k-linux-ld: kernel/power/qos.o: in function `arch_init_checked_vmap_ranges':
qos.c:(.init.text+0x0): multiple definition of `arch_init_checked_vmap_ranges'; init/main.o:main.c:(.init.text+0xa54): first defined here
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-05-11 5:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 18:25 [PATCH v5 1/2] mm: allow dynamic vmalloc range restrictions Maxwell Bland
2024-05-09 18:27 ` [PATCH v5 2/2] arm64: mm: code and data allocation partitioning Maxwell Bland
2024-05-11 4:56 ` [PATCH v5 1/2] mm: allow dynamic vmalloc range restrictions kernel test robot
2024-05-11 5:30 ` kernel test robot [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=202405111325.7IRuG4ZE-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=ardb@kernel.org \
--cc=ast@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=hch@infradead.org \
--cc=james.morse@arm.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@armlinux.org.uk \
--cc=lstoakes@gmail.com \
--cc=mark.rutland@arm.com \
--cc=martin.lau@linux.dev \
--cc=mbland@motorola.com \
--cc=mhiramat@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ryan.roberts@arm.com \
--cc=sdf@google.com \
--cc=shahuang@redhat.com \
--cc=song@kernel.org \
--cc=takakura@valinux.co.jp \
--cc=urezki@gmail.com \
--cc=will@kernel.org \
--cc=yonghong.song@linux.dev \
--cc=zlim.lnx@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).