|
Message-ID: <CAJcbSZFJD3JU2NMVfvNoAqvwE1L1pC-C6kfs7k6-DFk5pN3r4g@mail.gmail.com> Date: Thu, 12 May 2016 09:57:26 -0700 From: Thomas Garnier <thgarnie@...gle.com> To: kbuild test robot <lkp@...el.com> Cc: kbuild-all@...org, "H . Peter Anvin" <hpa@...or.com>, Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...e.de>, Andy Lutomirski <luto@...nel.org>, Dmitry Vyukov <dvyukov@...gle.com>, Paolo Bonzini <pbonzini@...hat.com>, Dan Williams <dan.j.williams@...el.com>, Kees Cook <keescook@...omium.org>, Stephen Smalley <sds@...ho.nsa.gov>, Kefeng Wang <wangkefeng.wang@...wei.com>, Jonathan Corbet <corbet@....net>, Matt Fleming <matt@...eblueprint.co.uk>, Toshi Kani <toshi.kani@....com>, Alexander Kuleshov <kuleshovmail@...il.com>, Alexander Popov <alpopov@...ecurity.com>, Joerg Roedel <jroedel@...e.de>, Dave Young <dyoung@...hat.com>, Baoquan He <bhe@...hat.com>, Dave Hansen <dave.hansen@...ux.intel.com>, Mark Salter <msalter@...hat.com>, Boris Ostrovsky <boris.ostrovsky@...cle.com>, x86@...nel.org, LKML <linux-kernel@...r.kernel.org>, linux-doc@...r.kernel.org, Greg Thelen <gthelen@...gle.com>, kernel-hardening@...ts.openwall.com Subject: Re: [PATCH v4 3/4] x86, boot: Implement ASLR for kernel memory sections (x86_64) Sorry about that. I will fix and send a new iteration this afternoon. Thomas On Thu, May 12, 2016 at 9:27 AM, kbuild test robot <lkp@...el.com> wrote: > Hi, > > [auto build test ERROR on next-20160512] > [cannot apply to tip/x86/core v4.6-rc7 v4.6-rc6 v4.6-rc5 v4.6-rc7] > [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] > > url: https://github.com/0day-ci/linux/commits/Thomas-Garnier/x86-boot-KASLR-memory-randomization/20160513-001319 > config: i386-tinyconfig (attached as .config) > compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430 > reproduce: > # save the attached .config to linux build tree > make ARCH=i386 > > Note: the linux-review/Thomas-Garnier/x86-boot-KASLR-memory-randomization/20160513-001319 HEAD cc523b95f012eb1d78508133b5b19b0a561ed3e1 builds fine. > It only hurts bisectibility. > > All errors (new ones prefixed by >>): > > arch/x86/mm/init.c: In function 'init_mem_mapping': >>> arch/x86/mm/init.c:595:2: error: 'trampoline_pgd_entry' undeclared (first use in this function) > trampoline_pgd_entry = init_level4_pgt[pgd_index(__PAGE_OFFSET)]; > ^~~~~~~~~~~~~~~~~~~~ > arch/x86/mm/init.c:595:2: note: each undeclared identifier is reported only once for each function it appears in >>> arch/x86/mm/init.c:595:25: error: 'init_level4_pgt' undeclared (first use in this function) > trampoline_pgd_entry = init_level4_pgt[pgd_index(__PAGE_OFFSET)]; > ^~~~~~~~~~~~~~~ > > vim +/trampoline_pgd_entry +595 arch/x86/mm/init.c > > 589 #endif > 590 > 591 /* the ISA range is always mapped regardless of memory holes */ > 592 init_memory_mapping(0, ISA_END_ADDRESS); > 593 > 594 /* Default trampoline pgd value */ > > 595 trampoline_pgd_entry = init_level4_pgt[pgd_index(__PAGE_OFFSET)]; > 596 > 597 /* Init the trampoline page table if needed for KASLR memory */ > 598 kaslr_trampoline_init(); > > --- > 0-DAY kernel test infrastructure Open Source Technology Center > https://lists.01.org/pipermail/kbuild-all Intel Corporation
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.