From: Minchan Kim <minchan@kernel.org>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [PATCH v7 2/7] mm: introduce external memory hinting API
Date: Tue, 3 Mar 2020 06:57:56 -0800 [thread overview]
Message-ID: <20200303145756.GA219683@google.com> (raw)
In-Reply-To: <202003031853.wHSB4BG2%lkp@intel.com>
On Tue, Mar 03, 2020 at 06:33:03PM +0800, kbuild test robot wrote:
> Hi Minchan,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on arm64/for-next/core]
> [also build test ERROR on arm/for-next m68k/for-next powerpc/next s390/features linus/master v5.6-rc4 next-20200302]
> [cannot apply to tip/x86/asm hp-parisc/for-next]
> [if your patch is applied to the wrong git tree, please drop us a note to help
> improve the system. BTW, we also suggest to use '--base' option to specify the
> base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
>
> url: https://github.com/0day-ci/linux/commits/Minchan-Kim/introduce-memory-hinting-API-for-external-process/20200303-044625
> base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
> config: arm64-defconfig (attached as .config)
> compiler: aarch64-linux-gcc (GCC) 7.5.0
> reproduce:
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # save the attached .config to linux build tree
> GCC_VERSION=7.5.0 make.cross ARCH=arm64
>
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
> aarch64-linux-ld: arch/arm64/kernel/head.o: relocation R_AARCH64_ABS32 against `_kernel_offset_le_lo32' can not be used when making a shared object
> aarch64-linux-ld: arch/arm64/kernel/efi-entry.stub.o: relocation R_AARCH64_ABS32 against `__efistub_stext_offset' can not be used when making a shared object
> arch/arm64/kernel/head.o: In function `kimage_vaddr':
> (.idmap.text+0x0): dangerous relocation: unsupported relocation
> arch/arm64/kernel/head.o: In function `__primary_switch':
> (.idmap.text+0x378): dangerous relocation: unsupported relocation
> (.idmap.text+0x380): dangerous relocation: unsupported relocation
> >> arch/arm64/kernel/sys32.o:(.rodata+0xdb8): undefined reference to `__arm64_process_madvise'
>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
Thanks. I guess I had a mistake so I hope this patch should fix the issue.
From 3cd8bc4dda41d13bcce6fcf6d9252ff684a1929d Mon Sep 17 00:00:00 2001
From: Minchan Kim <minchan@kernel.org>
Date: Tue, 3 Mar 2020 06:53:13 -0800
Subject: [PATCH] mm: fix process_madvise build break for arm64
0-day reported build break from process_madvise on ARM64.
aarch64-linux-ld: arch/arm64/kernel/head.o: relocation R_AARCH64_ABS32 against `_kernel_offset_le_lo32' can not be used when making a shared object
aarch64-linux-ld: arch/arm64/kernel/efi-entry.stub.o: relocation R_AARCH64_ABS32 against `__efistub_stext_offset' can not be used when making a shared object
arch/arm64/kernel/head.o: In function `kimage_vaddr':
(.idmap.text+0x0): dangerous relocation: unsupported relocation
arch/arm64/kernel/head.o: In function `__primary_switch':
(.idmap.text+0x378): dangerous relocation: unsupported relocation
(.idmap.text+0x380): dangerous relocation: unsupported relocation
>> arch/arm64/kernel/sys32.o:(.rodata+0xdb8): undefined reference to `__arm64_process_madvise'
This patch should fix it.
Reported-by: kbuild test robot <lkp@intel.com>
Signed-off-by: Minchan Kim <minchan@kernel.org>
---
arch/arm64/include/asm/unistd32.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/include/asm/unistd32.h b/arch/arm64/include/asm/unistd32.h
index 2a27be7a1f91..a1eec8d879d4 100644
--- a/arch/arm64/include/asm/unistd32.h
+++ b/arch/arm64/include/asm/unistd32.h
@@ -884,7 +884,7 @@ __SYSCALL(__NR_openat2, sys_openat2)
#define __NR_pidfd_getfd 438
__SYSCALL(__NR_pidfd_getfd, sys_pidfd_getfd)
#define __NR_process_madvise 439
-__SYSCALL(__NR_process_madvise, process_madvise)
+__SYSCALL(__NR_process_madvise, sys_process_madvise)
/*
* Please add new compat syscalls above this comment and update
--
2.25.1.481.gfbce0eb801-goog
next prev parent reply other threads:[~2020-03-03 14:58 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 19:36 [PATCH v7 0/7] introduce memory hinting API for external process Minchan Kim
2020-03-02 19:36 ` [PATCH v7 1/7] mm: pass task and mm to do_madvise Minchan Kim
2020-03-05 15:48 ` Vlastimil Babka
2020-05-08 18:21 ` Minchan Kim
2020-03-02 19:36 ` [PATCH v7 2/7] mm: introduce external memory hinting API Minchan Kim
2020-03-03 10:33 ` kbuild test robot
2020-03-03 14:57 ` Minchan Kim [this message]
2020-03-05 18:15 ` Vlastimil Babka
2020-03-10 22:20 ` Minchan Kim
2020-03-11 0:36 ` Minchan Kim
2020-03-12 12:40 ` Vlastimil Babka
2020-03-12 20:23 ` Minchan Kim
2020-05-08 18:33 ` Minchan Kim
2020-03-02 19:36 ` [PATCH v7 3/7] mm: check fatal signal pending of target process Minchan Kim
2020-03-06 10:22 ` Vlastimil Babka
2020-03-10 22:24 ` Minchan Kim
2020-03-02 19:36 ` [PATCH v7 4/7] pid: move pidfd_get_pid function to pid.c Minchan Kim
2020-03-06 10:57 ` Vlastimil Babka
2020-03-06 11:14 ` Christian Brauner
2020-03-02 19:36 ` [PATCH v7 5/7] mm: support both pid and pidfd for process_madvise Minchan Kim
2020-03-06 11:14 ` Vlastimil Babka
2020-03-11 0:42 ` Minchan Kim
2020-05-08 18:36 ` Minchan Kim
2020-05-08 23:04 ` Andrew Morton
2020-05-09 12:48 ` Christian Brauner
2020-05-09 23:14 ` Minchan Kim
2020-05-12 19:55 ` Suren Baghdasaryan
2020-03-02 19:36 ` [PATCH v7 6/7] mm/madvise: employ mmget_still_valid for write lock Minchan Kim
2020-03-06 12:52 ` Vlastimil Babka
2020-03-06 13:03 ` Oleksandr Natalenko
2020-03-06 16:03 ` Vlastimil Babka
2020-03-09 12:30 ` Oleksandr Natalenko
2020-03-10 22:28 ` Minchan Kim
2020-03-02 19:36 ` [PATCH v7 7/7] mm/madvise: allow KSM hints for remote API Minchan Kim
2020-03-06 13:13 ` Vlastimil Babka
2020-03-06 13:41 ` Oleksandr Natalenko
2020-03-06 16:08 ` Vlastimil Babka
2020-03-09 13:11 ` Oleksandr Natalenko
2020-03-09 15:08 ` Michal Hocko
2020-03-09 15:19 ` Oleksandr Natalenko
2020-03-09 15:42 ` Vlastimil Babka
2020-03-09 16:03 ` Michal Hocko
2020-06-11 2:21 ` Jann Horn
2020-03-02 21:16 ` [PATCH v7 0/7] introduce memory hinting API for external process Andrew Morton
2020-03-02 21:42 ` Minchan Kim
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=20200303145756.GA219683@google.com \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@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;
as well as URLs for NNTP newsgroup(s).