From: kbuild test robot <lkp@intel.com>
To: Kees Cook <keescook@chromium.org>
Cc: kbuild-all@01.org, Roman Gushchin <guro@fb.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [rgushchin:kmem_reparent.2 270/351] arch/arm64/include/asm/elf.h:117:3: error: implicit declaration of function 'is_compat_task'; did you mean 'is_idle_task'?
Date: Wed, 24 Apr 2019 17:56:50 +0800 [thread overview]
Message-ID: <201904241747.n64pZ9Up%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2075 bytes --]
tree: https://github.com/rgushchin/linux.git kmem_reparent.2
head: 9bcad55670928ba9722a8f9872d4db60d5bddea8
commit: 09d6592c219876dd21a11f1c3d35134ccb6937e1 [270/351] binfmt_elf: Update READ_IMPLIES_EXEC logic for modern CPUs
config: arm64-alldefconfig (attached as .config)
compiler: aarch64-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 09d6592c219876dd21a11f1c3d35134ccb6937e1
# save the attached .config to linux build tree
GCC_VERSION=7.2.0 make.cross ARCH=arm64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All error/warnings (new ones prefixed by >>):
In file included from include/linux/elf.h:5:0,
from include/linux/module.h:15,
from fs/binfmt_elf.c:12:
fs/binfmt_elf.c: In function 'load_elf_binary':
>> arch/arm64/include/asm/elf.h:117:3: error: implicit declaration of function 'is_compat_task'; did you mean 'is_idle_task'? [-Werror=implicit-function-declaration]
(is_compat_task() && stk == EXSTACK_DEFAULT)
^
>> fs/binfmt_elf.c:873:6: note: in expansion of macro 'elf_read_implies_exec'
if (elf_read_implies_exec(loc->elf_ex, executable_stack))
^~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +117 arch/arm64/include/asm/elf.h
109
110 /*
111 * 64-bit processes should not automatically gain READ_IMPLIES_EXEC. Only
112 * 32-bit processes without PT_GNU_STACK should trigger READ_IMPLIES_EXEC
113 * out of an abundance of caution against ancient toolchains not knowing
114 * how to mark memory protection flags correctly.
115 */
116 #define elf_read_implies_exec(ex, stk) \
> 117 (is_compat_task() && stk == EXSTACK_DEFAULT)
118
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 9387 bytes --]
reply other threads:[~2019-04-24 9:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201904241747.n64pZ9Up%lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=keescook@chromium.org \
--cc=linux-mm@kvack.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