From: kbuild test robot <lkp@intel.com>
To: Ram Pai <linuxram@us.ibm.com>
Cc: kbuild-all@01.org, mpe@ellerman.id.au, mingo@redhat.com,
akpm@linux-foundation.org, linuxppc-dev@lists.ozlabs.org,
linux-mm@kvack.org, x86@kernel.org, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org, dave.hansen@intel.com,
benh@kernel.crashing.org, paulus@samba.org,
khandual@linux.vnet.ibm.com, aneesh.kumar@linux.vnet.ibm.com,
bsingharora@gmail.com, hbabu@us.ibm.com, mhocko@kernel.org,
bauerman@linux.vnet.ibm.com, ebiederm@xmission.com,
corbet@lwn.net, arnd@arndb.de, fweimer@redhat.com,
msuchanek@suse.com
Subject: Re: [PATCH v11 3/3] mm, x86: display pkey in smaps only if arch supports pkeys
Date: Fri, 2 Feb 2018 12:27:27 +0800 [thread overview]
Message-ID: <201802021225.JPjLbdCs%fengguang.wu@intel.com> (raw)
In-Reply-To: <1517341452-11924-4-git-send-email-linuxram@us.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1633 bytes --]
Hi Ram,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.15 next-20180201]
[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/Ram-Pai/mm-x86-powerpc-Enhancements-to-Memory-Protection-Keys/20180202-120004
config: x86_64-randconfig-x005-201804 (attached as .config)
compiler: gcc-7 (Debian 7.2.0-12) 7.2.1 20171025
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All error/warnings (new ones prefixed by >>):
In file included from arch/x86/include/asm/mmu_context.h:8:0,
from arch/x86/events/core.c:36:
>> include/linux/pkeys.h:16:23: error: expected identifier or '(' before numeric constant
#define vma_pkey(vma) 0
^
>> arch/x86/include/asm/mmu_context.h:298:19: note: in expansion of macro 'vma_pkey'
static inline int vma_pkey(struct vm_area_struct *vma)
^~~~~~~~
vim +16 include/linux/pkeys.h
7
8 #ifdef CONFIG_ARCH_HAS_PKEYS
9 #include <asm/pkeys.h>
10 #else /* ! CONFIG_ARCH_HAS_PKEYS */
11 #define arch_max_pkey() (1)
12 #define execute_only_pkey(mm) (0)
13 #define arch_override_mprotect_pkey(vma, prot, pkey) (0)
14 #define PKEY_DEDICATED_EXECUTE_ONLY 0
15 #define ARCH_VM_PKEY_FLAGS 0
> 16 #define vma_pkey(vma) 0
17
---
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: 30449 bytes --]
next prev parent reply other threads:[~2018-02-02 4:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 19:44 [PATCH v11 0/3] mm, x86, powerpc: Enhancements to Memory Protection Keys Ram Pai
2018-01-30 19:44 ` [PATCH v11 1/3] mm, powerpc, x86: define VM_PKEY_BITx bits if CONFIG_ARCH_HAS_PKEYS is enabled Ram Pai
2018-01-30 19:44 ` [PATCH v11 2/3] mm, powerpc, x86: introduce an additional vma bit for powerpc pkey Ram Pai
2018-01-30 19:44 ` [PATCH v11 3/3] mm, x86: display pkey in smaps only if arch supports pkeys Ram Pai
2018-01-31 13:34 ` Michal Hocko
2018-02-02 4:27 ` kbuild test robot [this message]
2018-02-02 7:21 ` Ram Pai
2018-02-06 5:51 ` Michael Ellerman
2018-01-31 7:07 ` [PATCH v11 0/3] mm, x86, powerpc: Enhancements to Memory Protection Keys Ingo Molnar
2018-02-01 2:55 ` Michael Ellerman
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=201802021225.JPjLbdCs%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=arnd@arndb.de \
--cc=bauerman@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=bsingharora@gmail.com \
--cc=corbet@lwn.net \
--cc=dave.hansen@intel.com \
--cc=ebiederm@xmission.com \
--cc=fweimer@redhat.com \
--cc=hbabu@us.ibm.com \
--cc=kbuild-all@01.org \
--cc=khandual@linux.vnet.ibm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=linuxram@us.ibm.com \
--cc=mhocko@kernel.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=msuchanek@suse.com \
--cc=paulus@samba.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