From: kbuild test robot <lkp@intel.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: kbuild-all@01.org, linux-mm@kvack.org, akpm@linux-foundation.org,
mhocko@suse.com, zhongjiang@huawei.com,
labbott@fedoraproject.org, mark.rutland@arm.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] mm: huge-vmap: fail gracefully on unexpected huge vmap mappings
Date: Fri, 9 Jun 2017 15:45:09 +0800 [thread overview]
Message-ID: <201706091553.AtM2cOo2%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170608113548.24905-1-ard.biesheuvel@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1686 bytes --]
Hi Ard,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.12-rc4]
[cannot apply to next-20170608]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Ard-Biesheuvel/mm-huge-vmap-fail-gracefully-on-unexpected-huge-vmap-mappings/20170609-093900
config: i386-randconfig-i1-06042254 (attached as .config)
compiler: gcc-4.8 (Debian 4.8.4-1) 4.8.4
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
arch/x86/built-in.o: In function `vmalloc_fault':
>> fault.c:(.text.unlikely+0x1765): undefined reference to `pmd_huge'
mm/built-in.o: In function `follow_page_mask':
(.text+0x21da6): undefined reference to `pud_huge'
mm/built-in.o: In function `follow_page_mask':
(.text+0x21e39): undefined reference to `pmd_huge'
mm/built-in.o: In function `__follow_pte_pmd.isra.86':
memory.c:(.text+0x2381c): undefined reference to `pmd_huge'
memory.c:(.text+0x2384a): undefined reference to `pmd_huge'
mm/built-in.o: In function `apply_to_page_range':
(.text+0x2648d): undefined reference to `pud_huge'
mm/built-in.o: In function `apply_to_page_range':
(.text+0x26608): undefined reference to `pmd_huge'
mm/built-in.o: In function `vmalloc_to_page':
(.text+0x30ea3): undefined reference to `pud_huge'
mm/built-in.o: In function `vmalloc_to_page':
(.text+0x30ec8): undefined reference to `pmd_huge'
---
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: 27823 bytes --]
prev parent reply other threads:[~2017-06-09 7:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 11:35 [PATCH v3] mm: huge-vmap: fail gracefully on unexpected huge vmap mappings Ard Biesheuvel
2017-06-08 11:36 ` Ard Biesheuvel
2017-06-08 17:19 ` Dave Hansen
2017-06-08 12:59 ` Mark Rutland
2017-06-08 13:12 ` Ard Biesheuvel
2017-06-08 13:28 ` Mark Rutland
2017-06-08 14:51 ` Ard Biesheuvel
2017-06-08 16:37 ` Mark Rutland
2017-06-09 4:32 ` kbuild test robot
2017-06-09 7:45 ` kbuild 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=201706091553.AtM2cOo2%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=kbuild-all@01.org \
--cc=labbott@fedoraproject.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=mhocko@suse.com \
--cc=zhongjiang@huawei.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).