From: David Miller <davem@davemloft.net>
To: chenbofeng.kernel@gmail.com
Cc: netdev@vger.kernel.org, Selinux@tycho.nsa.gov,
linux-security-module@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 v6 0/5] bpf: security: New file mode and LSM hooks for eBPF object permission control
Date: Wed, 18 Oct 2017 14:11:55 +0100 (WEST) [thread overview]
Message-ID: <20171018.141155.1830215730026401984.davem@davemloft.net> (raw)
In-Reply-To: <20171018.134729.837318478487425125.davem@davemloft.net>
From: David Miller <davem@davemloft.net>
Date: Wed, 18 Oct 2017 13:47:29 +0100 (WEST)
> Series applied.
I had to revert as this breaks the build:
net/netfilter/xt_bpf.c: In function ‘__bpf_mt_check_path’:
net/netfilter/xt_bpf.c:59:7: error: too few arguments to function ‘bpf_obj_get_user’
fd = bpf_obj_get_user(path);
^~~~~~~~~~~~~~~~
next prev parent reply other threads:[~2017-10-18 13:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 19:11 [PATCH net-next v6 0/5] bpf: security: New file mode and LSM hooks for eBPF object permission control Chenbo Feng
2017-10-16 19:11 ` [PATCH net-next v6 1/5] bpf: Add file mode configuration into bpf maps Chenbo Feng
2017-10-16 22:59 ` Daniel Borkmann
2017-10-18 13:52 ` Daniel Borkmann
2017-10-16 19:11 ` [PATCH net-next v6 2/5] bpf: Add tests for eBPF file mode Chenbo Feng
2017-10-16 23:00 ` Daniel Borkmann
2017-10-16 19:11 ` [PATCH net-next v6 3/5] security: bpf: Add LSM hooks for bpf object related syscall Chenbo Feng
2017-10-16 19:11 ` [PATCH net-next v6 4/5] selinux: bpf: Add selinux check for eBPF syscall operations Chenbo Feng
2017-10-16 19:11 ` [PATCH net-next v6 5/5] selinux: bpf: Add addtional check for bpf object file receive Chenbo Feng
2017-10-18 12:47 ` [PATCH net-next v6 0/5] bpf: security: New file mode and LSM hooks for eBPF object permission control David Miller
2017-10-18 13:11 ` David Miller [this message]
2017-10-19 1:49 ` James Morris
2017-10-19 9:48 ` Daniel Borkmann
2017-10-19 11:00 ` David Miller
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=20171018.141155.1830215730026401984.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Selinux@tycho.nsa.gov \
--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=linux-security-module@vger.kernel.org \
--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).