From: Michal Hocko <mhocko@kernel.org>
To: Kees Cook <keescook@chromium.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: next: s390 allyesconfig fails to compile samples/seccomp
Date: Fri, 6 Jan 2017 16:04:17 +0100 [thread overview]
Message-ID: <20170106150417.GQ5556@dhcp22.suse.cz> (raw)
Hi,
I am not relly sure what went wrong, but I've noticed that allyesconfig
doesn't compile with my s390 crosscompiler with a strange error
messages for linux-next (next-20170106). Linus' tree compiles just fine.
It smells like some headers include problems because
$ git diff origin/master..next/master -- samples/seccomp/
doesn't show anything...
samples/seccomp/bpf-helper.h:134:2: error: #error __BITS_PER_LONG value unusable.
#error __BITS_PER_LONG value unusable.
^
In file included from samples/seccomp/bpf-fancy.c:12:0:
samples/seccomp/bpf-fancy.c: In function ‘main’:
samples/seccomp/bpf-fancy.c:37:11: error: ‘__NR_exit’ undeclared (first use in this function)
SYSCALL(__NR_exit, ALLOW),
^
./usr/include/linux/filter.h:51:69: note: in definition of macro ‘BPF_JUMP’
#define BPF_JUMP(code, k, jt, jf) { (unsigned short)(code), jt, jf, k }
^
samples/seccomp/bpf-fancy.c:37:3: note: in expansion of macro ‘SYSCALL’
SYSCALL(__NR_exit, ALLOW),
^
samples/seccomp/bpf-fancy.c:37:11: note: each undeclared identifier is reported only once for each function it appears in
SYSCALL(__NR_exit, ALLOW),
^
./usr/include/linux/filter.h:51:69: note: in definition of macro ‘BPF_JUMP’
#define BPF_JUMP(code, k, jt, jf) { (unsigned short)(code), jt, jf, k }
^
samples/seccomp/bpf-fancy.c:37:3: note: in expansion of macro ‘SYSCALL’
SYSCALL(__NR_exit, ALLOW),
^
samples/seccomp/bpf-fancy.c:38:11: error: ‘__NR_exit_group’ undeclared (first use in this function)
SYSCALL(__NR_exit_group, ALLOW),
^
./usr/include/linux/filter.h:51:69: note: in definition of macro ‘BPF_JUMP’
#define BPF_JUMP(code, k, jt, jf) { (unsigned short)(code), jt, jf, k }
^
samples/seccomp/bpf-fancy.c:38:3: note: in expansion of macro ‘SYSCALL’
SYSCALL(__NR_exit_group, ALLOW),
^
samples/seccomp/bpf-fancy.c:39:11: error: ‘__NR_write’ undeclared (first use in this function)
SYSCALL(__NR_write, JUMP(&l, write_fd)),
^
./usr/include/linux/filter.h:51:69: note: in definition of macro ‘BPF_JUMP’
#define BPF_JUMP(code, k, jt, jf) { (unsigned short)(code), jt, jf, k }
^
samples/seccomp/bpf-fancy.c:39:3: note: in expansion of macro ‘SYSCALL’
SYSCALL(__NR_write, JUMP(&l, write_fd)),
--
Michal Hocko
SUSE Labs
next reply other threads:[~2017-01-06 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 15:04 Michal Hocko [this message]
2017-01-06 20:18 ` Kees Cook
2017-01-06 20:53 ` Kees Cook
2017-01-07 10:21 ` Michal Hocko
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=20170106150417.GQ5556@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®