public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Tyler Hicks <tyhicks@canonical.com>
Cc: kbuild-all@01.org, Paul Moore <paul@paul-moore.com>,
	Eric Paris <eparis@redhat.com>, Kees Cook <keescook@chromium.org>,
	Andy Lutomirski <luto@amacapital.net>,
	Will Drewry <wad@chromium.org>,
	linux-audit@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] seccomp: Create an action to audit before allowing
Date: Tue, 3 Jan 2017 04:32:37 +0800	[thread overview]
Message-ID: <201701030431.CKnL8B72%fengguang.wu@intel.com> (raw)
In-Reply-To: <1483377999-15019-2-git-send-email-tyhicks@canonical.com>

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

Hi Tyler,

[auto build test ERROR on linus/master]
[also build test ERROR on v4.10-rc2 next-20161224]
[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/Tyler-Hicks/seccomp-Create-an-action-to-audit-before-allowing/20170103-041342
config: i386-randconfig-x003-201701 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

   kernel/seccomp.c: In function '__seccomp_filter':
>> kernel/seccomp.c:634:3: error: implicit declaration of function 'audit_seccomp_common' [-Werror=implicit-function-declaration]
      audit_seccomp_common(this_syscall, action);
      ^~~~~~~~~~~~~~~~~~~~
   cc1: some warnings being treated as errors

vim +/audit_seccomp_common +634 kernel/seccomp.c

   628			if (__seccomp_filter(this_syscall, NULL, true))
   629				return -1;
   630	
   631			return 0;
   632	
   633		case SECCOMP_RET_AUDIT:
 > 634			audit_seccomp_common(this_syscall, action);
   635			return 0;
   636	
   637		case SECCOMP_RET_ALLOW:

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

  reply	other threads:[~2017-01-02 20:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-02 17:26 [PATCH 0/2] Support auditing while still allowing a syscall Tyler Hicks
2017-01-02 17:26 ` [PATCH 1/2] seccomp: Create an action to audit before allowing Tyler Hicks
2017-01-02 20:32   ` kbuild test robot [this message]
2017-01-02 17:26 ` [PATCH 2/2] seccomp: Add tests for SECCOMP_RET_AUDIT Tyler Hicks

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=201701030431.CKnL8B72%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=eparis@redhat.com \
    --cc=kbuild-all@01.org \
    --cc=keescook@chromium.org \
    --cc=linux-audit@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=paul@paul-moore.com \
    --cc=tyhicks@canonical.com \
    --cc=wad@chromium.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