From: David Miller <davem@davemloft.net>
To: chenbofeng.kernel@gmail.com
Cc: netdev@vger.kernel.org, jeffv@google.com,
alexei.starovoitov@gmail.com, lorenzo@google.com,
daniel@iogearbox.net, sds@tycho.nsa.gov,
james.l.morris@oracle.com, paul@paul-moore.com, fengc@google.com
Subject: Re: [PATCH net-next v5 0/5] bpf: security: New file mode and LSM hooks for eBPF object permission control
Date: Sat, 14 Oct 2017 11:27:53 -0700 (PDT) [thread overview]
Message-ID: <20171014.112753.925194737261973271.davem@davemloft.net> (raw)
In-Reply-To: <20171012205510.36028-1-chenbofeng.kernel@gmail.com>
Hmmm, this doesn't build for me:
security/selinux/hooks.c: In function ‘bpf_fd_pass’:
security/selinux/hooks.c:6325:40: error: ‘SECCLASS_BPF_MAP’ undeclared (first use in this function); did you mean ‘SECCLASS_BPF’?
ret = avc_has_perm(sid, bpfsec->sid, SECCLASS_BPF_MAP,
^~~~~~~~~~~~~~~~
SECCLASS_BPF
security/selinux/hooks.c:6325:40: note: each undeclared identifier is reported only once for each function it appears in
security/selinux/hooks.c:6332:40: error: ‘SECCLASS_BPF_PROG’ undeclared (first use in this function); did you mean ‘SECCLASS_BPF_MAP’?
ret = avc_has_perm(sid, bpfsec->sid, SECCLASS_BPF_PROG,
^~~~~~~~~~~~~~~~~
SECCLASS_BPF_MAP
prev parent reply other threads:[~2017-10-14 18:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 20:55 [PATCH net-next v5 0/5] bpf: security: New file mode and LSM hooks for eBPF object permission control Chenbo Feng
2017-10-12 20:55 ` [PATCH net-next v5 1/5] bpf: Add file mode configuration into bpf maps Chenbo Feng
2017-10-12 20:55 ` [PATCH net-next v5 2/5] bpf: Add tests for eBPF file mode Chenbo Feng
2017-10-12 20:55 ` [PATCH net-next v5 3/5] security: bpf: Add LSM hooks for bpf object related syscall Chenbo Feng
2017-10-12 20:55 ` [PATCH net-next v5 4/5] selinux: bpf: Add selinux check for eBPF syscall operations Chenbo Feng
2017-10-13 19:40 ` Stephen Smalley
2017-10-12 20:55 ` [PATCH net-next v5 5/5] selinux: bpf: Add addtional check for bpf object file receive Chenbo Feng
2017-10-13 19:59 ` Stephen Smalley
2017-10-16 16:34 ` Stephen Smalley
2017-10-16 19:03 ` Chenbo Feng
2017-10-14 18:27 ` David Miller [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=20171014.112753.925194737261973271.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexei.starovoitov@gmail.com \
--cc=chenbofeng.kernel@gmail.com \
--cc=daniel@iogearbox.net \
--cc=fengc@google.com \
--cc=james.l.morris@oracle.com \
--cc=jeffv@google.com \
--cc=lorenzo@google.com \
--cc=netdev@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=sds@tycho.nsa.gov \
/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).