linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Nayna Jain <nayna@linux.vnet.ibm.com>
Cc: kbuild-all@01.org, linux-integrity@vger.kernel.org,
	zohar@linux.ibm.com, linux-security-module@vger.kernel.org,
	linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
	dhowells@redhat.com, jforbes@redhat.com,
	Eric Richter <erichte@linux.vnet.ibm.com>,
	Nayna Jain <nayna@linux.vnet.ibm.com>
Subject: Re: [PATCH v2 6/6] x86/ima: define arch_get_ima_policy() for x86
Date: Fri, 14 Sep 2018 21:50:31 +0800	[thread overview]
Message-ID: <201809142126.oa45Rj76%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180914080005.6138-7-nayna@linux.vnet.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 1453 bytes --]

Hi Eric,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on integrity/next-integrity]
[also build test ERROR on v4.19-rc3 next-20180913]
[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/Nayna-Jain/Add-support-for-architecture-specific-IMA-policies/20180914-202254
base:   https://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git next-integrity
config: i386-randconfig-s1-201836 (attached as .config)
compiler: gcc-6 (Debian 6.4.0-9) 6.4.0 20171026
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

>> arch/x86//kernel/ima_arch.c:28:21: error: redefinition of 'arch_get_ima_policy'
    const char * const *arch_get_ima_policy(void)
                        ^~~~~~~~~~~~~~~~~~~
   In file included from arch/x86//kernel/ima_arch.c:6:0:
   include/linux/ima.h:45:35: note: previous definition of 'arch_get_ima_policy' was here
    static inline const char * const *arch_get_ima_policy(void)
                                      ^~~~~~~~~~~~~~~~~~~

vim +/arch_get_ima_policy +28 arch/x86//kernel/ima_arch.c

    27	
  > 28	const char * const *arch_get_ima_policy(void)

---
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: 28312 bytes --]

      reply	other threads:[~2018-09-14 13:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-14  7:59 [PATCH v2 0/6] Add support for architecture specific IMA policies Nayna Jain
2018-09-14  8:00 ` [PATCH v2 1/6] ima: define arch_ima_get_secureboot Nayna Jain
2018-09-14  8:00 ` [PATCH v2 2/6] ima: prevent kexec_load syscall based on runtime secureboot flag Nayna Jain
2018-09-14  8:00 ` [PATCH v2 3/6] ima: refactor ima_init_policy() Nayna Jain
2018-09-14  8:00 ` [PATCH v2 4/6] ima: add support for arch specific policies Nayna Jain
2018-09-14  8:00 ` [PATCH v2 5/6] ima: add support for external setting of ima_appraise Nayna Jain
2018-09-14  8:00 ` [PATCH v2 6/6] x86/ima: define arch_get_ima_policy() for x86 Nayna Jain
2018-09-14 13:50   ` 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=201809142126.oa45Rj76%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=dhowells@redhat.com \
    --cc=erichte@linux.vnet.ibm.com \
    --cc=jforbes@redhat.com \
    --cc=kbuild-all@01.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=nayna@linux.vnet.ibm.com \
    --cc=zohar@linux.ibm.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).