From: kbuild test robot <lkp@intel.com>
To: Tycho Andersen <tycho.andersen@canonical.com>
Cc: kbuild-all@01.org, Kees Cook <keescook@chromium.org>,
Alexei Starovoitov <ast@kernel.org>,
Will Drewry <wad@chromium.org>, Oleg Nesterov <oleg@redhat.com>,
Andy Lutomirski <luto@amacapital.net>,
Pavel Emelyanov <xemul@parallels.com>,
"Serge E. Hallyn" <serge.hallyn@ubuntu.com>,
Daniel Borkmann <daniel@iogearbox.net>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-api@vger.kernel.org,
Tycho Andersen <tycho.andersen@canonical.com>
Subject: Re: [PATCH v3 2/5] seccomp: add the concept of a seccomp filter FD
Date: Thu, 1 Oct 2015 02:29:25 +0800 [thread overview]
Message-ID: <201510010231.ibjcmDLo%fengguang.wu@intel.com> (raw)
In-Reply-To: <1443636820-17083-3-git-send-email-tycho.andersen@canonical.com>
[-- Attachment #1: Type: text/plain, Size: 1765 bytes --]
Hi Tycho,
[auto build test results on v4.3-rc3 -- if it's inappropriate base, please ignore]
config: i386-alldefconfig (attached as .config)
reproduce:
git checkout 9613ae6bf5f111701614acb3eda3123d21a59239
# save the attached .config to linux build tree
make ARCH=i386
All error/warnings (new ones prefixed by >>):
>> kernel/seccomp.c:998:10: error: expected ';', ',' or ')' before 'const'
const char __user *filter)
^
kernel/seccomp.c: In function 'do_seccomp':
>> kernel/seccomp.c:1016:10: error: implicit declaration of function 'seccomp_filter_fd' [-Werror=implicit-function-declaration]
return seccomp_filter_fd(flags, uargs);
^
cc1: some warnings being treated as errors
vim +998 kernel/seccomp.c
992 const char __user *filter)
993 {
994 return -EINVAL;
995 }
996
997 static inline long seccomp_filter_fd(unsigned int flags
> 998 const char __user *filter)
999 {
1000 return -EINVAL;
1001 }
1002 #endif
1003
1004 /* Common entry point for both prctl and syscall. */
1005 static long do_seccomp(unsigned int op, unsigned int flags,
1006 const char __user *uargs)
1007 {
1008 switch (op) {
1009 case SECCOMP_SET_MODE_STRICT:
1010 if (flags != 0 || uargs != NULL)
1011 return -EINVAL;
1012 return seccomp_set_mode_strict();
1013 case SECCOMP_SET_MODE_FILTER:
1014 return seccomp_set_mode_filter(flags, uargs);
1015 case SECCOMP_FILTER_FD:
> 1016 return seccomp_filter_fd(flags, uargs);
1017 default:
1018 return -EINVAL;
1019 }
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 9474 bytes --]
next prev parent reply other threads:[~2015-09-30 18:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 18:13 checkpoint/restore of seccomp filters v3 Tycho Andersen
2015-09-30 18:13 ` [PATCH v3 1/5] seccomp: save the original filter Tycho Andersen
2015-09-30 18:13 ` [PATCH v3 2/5] seccomp: add the concept of a seccomp filter FD Tycho Andersen
2015-09-30 18:27 ` Andy Lutomirski
2015-09-30 18:36 ` Tycho Andersen
2015-09-30 18:47 ` Andy Lutomirski
2015-09-30 18:29 ` kbuild test robot [this message]
2015-09-30 18:13 ` [PATCH v3 3/5] seccomp: add a ptrace command to get seccomp filter fds Tycho Andersen
2015-09-30 18:13 ` [PATCH v3 4/5] kcmp: add KCMP_FILE_PRIVATE_DATA Tycho Andersen
2015-09-30 18:25 ` Andy Lutomirski
2015-09-30 18:41 ` Tycho Andersen
2015-09-30 18:47 ` Andy Lutomirski
2015-09-30 18:55 ` Tycho Andersen
2015-09-30 18:56 ` Andy Lutomirski
2015-09-30 21:39 ` Tycho Andersen
2015-09-30 21:48 ` Andy Lutomirski
2015-09-30 22:10 ` Tycho Andersen
2015-10-01 16:45 ` Tycho Andersen
2015-09-30 18:13 ` [PATCH v3 5/5] bpf: save the program the user actually supplied Tycho Andersen
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=201510010231.ibjcmDLo%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=kbuild-all@01.org \
--cc=keescook@chromium.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=netdev@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=serge.hallyn@ubuntu.com \
--cc=tycho.andersen@canonical.com \
--cc=wad@chromium.org \
--cc=xemul@parallels.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
all inboxes | Powered by JetHome®