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 253/327] fs/binfmt_elf.c:1140:7: error: 'elf_interpreter' undeclared; did you mean 'interpreter'?
Date: Sun, 21 Apr 2019 08:31:46 +0800 [thread overview]
Message-ID: <201904210843.GsCAmfWV%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2836 bytes --]
tree: https://github.com/rgushchin/linux.git kmem_reparent.2
head: 3239ac71c274fa41b651ec92e43cbb18cc5b8112
commit: e0477c3bfa481937438fa6733bcb70e1d8f3d1a9 [253/327] fs/binfmt_elf.c: move brk out of mmap when doing direct loader exec
config: x86_64-randconfig-h1-201915 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
git checkout e0477c3bfa481937438fa6733bcb70e1d8f3d1a9
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
Note: the rgushchin/kmem_reparent.2 HEAD 3239ac71c274fa41b651ec92e43cbb18cc5b8112 builds fine.
It only hurts bisectibility.
All errors (new ones prefixed by >>):
fs/binfmt_elf.c: In function 'load_elf_binary':
>> fs/binfmt_elf.c:1140:7: error: 'elf_interpreter' undeclared (first use in this function); did you mean 'interpreter'?
if (!elf_interpreter)
^~~~~~~~~~~~~~~
interpreter
fs/binfmt_elf.c:1140:7: note: each undeclared identifier is reported only once for each function it appears in
vim +1140 fs/binfmt_elf.c
1122
1123 retval = create_elf_tables(bprm, &loc->elf_ex,
1124 load_addr, interp_load_addr);
1125 if (retval < 0)
1126 goto out;
1127 /* N.B. passed_fileno might not be initialized? */
1128 current->mm->end_code = end_code;
1129 current->mm->start_code = start_code;
1130 current->mm->start_data = start_data;
1131 current->mm->end_data = end_data;
1132 current->mm->start_stack = bprm->p;
1133
1134 /*
1135 * When executing a loader directly (ET_DYN without Interp), move
1136 * the brk area out of the mmap region (since it grows up, and may
1137 * collide early with the stack growing down), and into the unused
1138 * ELF_ET_DYN_BASE region.
1139 */
> 1140 if (!elf_interpreter)
1141 current->mm->brk = current->mm->start_brk = ELF_ET_DYN_BASE;
1142
1143 if ((current->flags & PF_RANDOMIZE) && (randomize_va_space > 1)) {
1144 current->mm->brk = current->mm->start_brk =
1145 arch_randomize_brk(current->mm);
1146 #ifdef compat_brk_randomized
1147 current->brk_randomized = 1;
1148 #endif
1149 }
1150
1151 if (current->personality & MMAP_PAGE_ZERO) {
1152 /* Why this, you ask??? Well SVr4 maps page 0 as read-only,
1153 and some applications "depend" upon this behavior.
1154 Since we do not have the power to recompile these, we
1155 emulate the SVr4 behavior. Sigh. */
1156 error = vm_mmap(NULL, 0, PAGE_SIZE, PROT_READ | PROT_EXEC,
1157 MAP_FIXED | MAP_PRIVATE, 0);
1158 }
1159
---
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: 31485 bytes --]
reply other threads:[~2019-04-21 0:31 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=201904210843.GsCAmfWV%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