From: daniel@iogearbox.net (Daniel Borkmann)
To: linux-security-module@vger.kernel.org
Subject: [PATCH net-next v6 0/5] bpf: security: New file mode and LSM hooks for eBPF object permission control
Date: Thu, 19 Oct 2017 11:48:33 +0200 [thread overview]
Message-ID: <59E874F1.6040609@iogearbox.net> (raw)
In-Reply-To: <alpine.LFD.2.20.1710191248100.1108@t440.gateway.2wire.net>
On 10/19/2017 03:49 AM, James Morris wrote:
> On Wed, 18 Oct 2017, David Miller wrote:
>
>> Series applied.
>
> I hadn't gotten to reviewing this patchset yet.
>
> Please wait for more acks/reviews from LSM folk for things touching
> security/, next time.
It didn't get applied yet due to a build error, v7 is pending here
if you want to take a look (the series is already on the lists with
multiple feedback rounds since beginning of Oct):
http://patchwork.ozlabs.org/project/netdev/list/?series=8967
Thanks,
Daniel
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Borkmann <daniel@iogearbox.net>
To: James Morris <james.l.morris@oracle.com>,
David Miller <davem@davemloft.net>
Cc: chenbofeng.kernel@gmail.com, netdev@vger.kernel.org,
Selinux@tycho.nsa.gov, linux-security-module@vger.kernel.org,
jeffv@google.com, alexei.starovoitov@gmail.com,
lorenzo@google.com, sds@tycho.nsa.gov, 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: Thu, 19 Oct 2017 11:48:33 +0200 [thread overview]
Message-ID: <59E874F1.6040609@iogearbox.net> (raw)
In-Reply-To: <alpine.LFD.2.20.1710191248100.1108@t440.gateway.2wire.net>
On 10/19/2017 03:49 AM, James Morris wrote:
> On Wed, 18 Oct 2017, David Miller wrote:
>
>> Series applied.
>
> I hadn't gotten to reviewing this patchset yet.
>
> Please wait for more acks/reviews from LSM folk for things touching
> security/, next time.
It didn't get applied yet due to a build error, v7 is pending here
if you want to take a look (the series is already on the lists with
multiple feedback rounds since beginning of Oct):
http://patchwork.ozlabs.org/project/netdev/list/?series=8967
Thanks,
Daniel
next prev parent reply other threads:[~2017-10-19 9:48 UTC|newest]
Thread overview: 28+ 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 ` 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 19:11 ` Chenbo Feng
2017-10-16 22:59 ` Daniel Borkmann
2017-10-16 22:59 ` Daniel Borkmann
2017-10-18 13:52 ` 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 19:11 ` Chenbo Feng
2017-10-16 23:00 ` Daniel Borkmann
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 ` 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 ` 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-16 19:11 ` 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 12:47 ` David Miller
2017-10-18 13:11 ` David Miller
2017-10-18 13:11 ` David Miller
2017-10-19 1:49 ` James Morris
2017-10-19 1:49 ` James Morris
2017-10-19 9:48 ` Daniel Borkmann [this message]
2017-10-19 9:48 ` Daniel Borkmann
2017-10-19 11:00 ` David Miller
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=59E874F1.6040609@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=linux-security-module@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.