From: kbuild test robot <lkp@intel.com>
To: Dave Hansen <dave.hansen@linux.intel.com>
Cc: kbuild-all@01.org, dave.hansen@intel.com, x86@kernel.org,
Dave Hansen <dave.hansen@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 3/5] mm: remove MPX hooks from generic code
Date: Sat, 5 Jan 2019 06:33:13 +0800 [thread overview]
Message-ID: <201901050618.H86nOzMU%fengguang.wu@intel.com> (raw)
Message-ID: <20190104223313.MKO2m2Zm-pAeM0byK8AsIDRAH1Y5B5gN1OhXnUkUqK0@z> (raw)
In-Reply-To: <1546624183-26543-4-git-send-email-dave.hansen@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 4030 bytes --]
Hi Dave,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.20 next-20190103]
[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/Dave-Hansen/x86-mpx-remove-MPX-APIs/20190105-051028
config: i386-tinyconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
Note: the linux-review/Dave-Hansen/x86-mpx-remove-MPX-APIs/20190105-051028 HEAD 34ce15ccc190201bc8c062e1559df2c1864902ef builds fine.
It only hurts bisectibility.
All errors (new ones prefixed by >>):
arch/x86/kernel/setup.c: In function 'setup_arch':
>> arch/x86/kernel/setup.c:927:2: error: implicit declaration of function 'mpx_mm_init'; did you mean 'mem_init'? [-Werror=implicit-function-declaration]
mpx_mm_init(&init_mm);
^~~~~~~~~~~
mem_init
cc1: some warnings being treated as errors
vim +927 arch/x86/kernel/setup.c
7465252ea arch/x86/kernel/setup_32.c Yinghai Lu 2008-06-23 911
42bbdb43b arch/x86/kernel/setup.c Thomas Gleixner 2009-08-20 912 x86_init.oem.arch_setup();
2215e69d2 arch/x86/kernel/setup_32.c Huang, Ying 2008-01-30 913
419afdf53 arch/x86/kernel/setup.c Bjorn Helgaas 2010-10-26 914 iomem_resource.end = (1ULL << boot_cpu_data.x86_phys_bits) - 1;
103e20630 arch/x86/kernel/setup.c Ingo Molnar 2017-01-28 915 e820__memory_setup();
28bb22379 arch/x86/kernel/setup.c Yinghai Lu 2008-06-30 916 parse_setup_data();
28bb22379 arch/x86/kernel/setup.c Yinghai Lu 2008-06-30 917
^1da177e4 arch/i386/kernel/setup.c Linus Torvalds 2005-04-16 918 copy_edd();
^1da177e4 arch/i386/kernel/setup.c Linus Torvalds 2005-04-16 919
30c826451 arch/x86/kernel/setup_32.c H. Peter Anvin 2007-10-15 920 if (!boot_params.hdr.root_flags)
^1da177e4 arch/i386/kernel/setup.c Linus Torvalds 2005-04-16 921 root_mountflags &= ~MS_RDONLY;
^1da177e4 arch/i386/kernel/setup.c Linus Torvalds 2005-04-16 922 init_mm.start_code = (unsigned long) _text;
^1da177e4 arch/i386/kernel/setup.c Linus Torvalds 2005-04-16 923 init_mm.end_code = (unsigned long) _etext;
^1da177e4 arch/i386/kernel/setup.c Linus Torvalds 2005-04-16 924 init_mm.end_data = (unsigned long) _edata;
93dbda7cb arch/x86/kernel/setup.c Jeremy Fitzhardinge 2009-02-26 925 init_mm.brk = _brk_end;
fe3d197f8 arch/x86/kernel/setup.c Dave Hansen 2014-11-14 926
fe3d197f8 arch/x86/kernel/setup.c Dave Hansen 2014-11-14 @927 mpx_mm_init(&init_mm);
^1da177e4 arch/i386/kernel/setup.c Linus Torvalds 2005-04-16 928
4046d6e81 arch/x86/kernel/setup.c Linus Torvalds 2016-04-14 929 code_resource.start = __pa_symbol(_text);
4046d6e81 arch/x86/kernel/setup.c Linus Torvalds 2016-04-14 930 code_resource.end = __pa_symbol(_etext)-1;
4046d6e81 arch/x86/kernel/setup.c Linus Torvalds 2016-04-14 931 data_resource.start = __pa_symbol(_etext);
4046d6e81 arch/x86/kernel/setup.c Linus Torvalds 2016-04-14 932 data_resource.end = __pa_symbol(_edata)-1;
4046d6e81 arch/x86/kernel/setup.c Linus Torvalds 2016-04-14 933 bss_resource.start = __pa_symbol(__bss_start);
4046d6e81 arch/x86/kernel/setup.c Linus Torvalds 2016-04-14 934 bss_resource.end = __pa_symbol(__bss_stop)-1;
4046d6e81 arch/x86/kernel/setup.c Linus Torvalds 2016-04-14 935
:::::: The code at line 927 was first introduced by commit
:::::: fe3d197f84319d3bce379a9c0dc17b1f48ad358c x86, mpx: On-demand kernel allocation of bounds tables
:::::: TO: Dave Hansen <dave.hansen@linux.intel.com>
:::::: CC: Thomas Gleixner <tglx@linutronix.de>
---
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: 6543 bytes --]
next prev parent reply other threads:[~2019-01-04 22:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 17:49 [RFC][v2] x86: remove Intel MPX Dave Hansen
2019-01-04 17:49 ` [PATCH 1/5] x86/mpx: remove MPX APIs Dave Hansen
2019-01-04 17:49 ` [PATCH 2/5] x86/mpx: remove bounds exception code Dave Hansen
2019-01-04 17:49 ` [PATCH 3/5] mm: remove MPX hooks from generic code Dave Hansen
2019-01-04 22:33 ` kbuild test robot [this message]
2019-01-04 22:33 ` kbuild test robot
2019-01-04 17:49 ` [PATCH 4/5] x86/mpx: remove build infratsructure Dave Hansen
2019-01-04 17:49 ` [PATCH 5/5] x86/mpx: remove MPX from arch/x86 Dave Hansen
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=201901050618.H86nOzMU%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=x86@kernel.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