From: Andy Lutomirski <luto@amacapital.net>
To: Tycho Andersen <tycho@tycho.ws>
Cc: Kees Cook <keescook@chromium.org>,
linux-kernel@vger.kernel.org,
containers@lists.linux-foundation.org, linux-api@vger.kernel.org,
Oleg Nesterov <oleg@redhat.com>,
"Eric W . Biederman" <ebiederm@xmission.com>,
"Serge E . Hallyn" <serge@hallyn.com>,
Christian Brauner <christian.brauner@ubuntu.com>,
Tyler Hicks <tyhicks@canonical.com>,
Akihiro Suda <suda.akihiro@lab.ntt.co.jp>,
"Tobin C . Harding" <me@tobin.cc>
Subject: Re: [PATCH v4 0/4] seccomp trap to userspace
Date: Mon, 6 Aug 2018 19:57:16 -0700 [thread overview]
Message-ID: <62CE9671-DECD-415B-8F57-9FCCE7922990@amacapital.net> (raw)
In-Reply-To: <20180807024442.GA12274@cisco.lan>
> On Aug 6, 2018, at 7:44 PM, Tycho Andersen <tycho@tycho.ws> wrote:
>
> Hi all,
>
> Dinesh Subhraveti has claimed that some part of this series might be
> patented. While he has not furnished me with anything to confirm this
> claim, I'll put this series on hold.
That... is utterly ridiculous. Does LF have a mechanism to figure out wtf and deal with it by, for example, filing for ex parte review.
Every microkernel ever should strongly resemble prior art.
>
> Tycho
>
>> On Thu, Jun 21, 2018 at 04:04:12PM -0600, Tycho Andersen wrote:
>> Hi all,
>>
>> Here's v4 of the seccomp trap to userspace series. v3 is here:
>> https://lkml.org/lkml/2018/5/31/527
>>
>> I believe we've addressed the two burning questions I had about v3: 1.
>> it seems ok not to use netlink, since there's not a great way to re-use
>> the API without a lot of unnecessary code and 2. only having return
>> capability for fds seems fine with people. Or at least I haven't heard
>> any strong objections.
>>
>> I've re-worked a bunch of things in this version based on feedback from
>> the last series. See patch notes for details. At this point I'm not
>> aware of anything that needs to be addressed, but of course that is
>> subject to change :)
>>
>> Tycho
>>
>> Tycho Andersen (4):
>> seccomp: add a return code to trap to userspace
>> seccomp: make get_nth_filter available outside of CHECKPOINT_RESTORE
>> seccomp: add a way to get a listener fd from ptrace
>> seccomp: add support for passing fds via USER_NOTIF
>>
>> .../userspace-api/seccomp_filter.rst | 79 +++
>> arch/Kconfig | 7 +
>> include/linux/seccomp.h | 18 +-
>> include/uapi/linux/ptrace.h | 2 +
>> include/uapi/linux/seccomp.h | 23 +-
>> kernel/ptrace.c | 4 +
>> kernel/seccomp.c | 491 ++++++++++++++-
>> tools/testing/selftests/seccomp/seccomp_bpf.c | 560 +++++++++++++++++-
>> 8 files changed, 1172 insertions(+), 12 deletions(-)
>>
>> --
>> 2.17.1
>>
next prev parent reply other threads:[~2018-08-07 2:57 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 22:04 [PATCH v4 0/4] seccomp trap to userspace Tycho Andersen
2018-06-21 22:04 ` [PATCH v4 1/4] seccomp: add a return code to " Tycho Andersen
2018-06-21 23:21 ` Jann Horn
2018-06-22 0:58 ` Tycho Andersen
2018-06-22 1:28 ` Jann Horn
2018-06-22 1:39 ` Tycho Andersen
2018-06-22 14:40 ` Jann Horn
2018-06-22 15:15 ` Tycho Andersen
2018-06-22 16:24 ` Jann Horn
2018-06-22 18:09 ` Andy Lutomirski
2018-06-22 21:51 ` Kees Cook
2018-06-22 22:27 ` Jann Horn
2018-06-26 1:32 ` Tycho Andersen
2018-06-26 2:00 ` Andy Lutomirski
2018-06-21 22:04 ` [PATCH v4 2/4] seccomp: make get_nth_filter available outside of CHECKPOINT_RESTORE Tycho Andersen
2018-06-21 22:04 ` [PATCH v4 3/4] seccomp: add a way to get a listener fd from ptrace Tycho Andersen
2018-06-21 22:48 ` Jann Horn
2018-06-21 23:07 ` Tycho Andersen
2018-06-21 22:04 ` [PATCH v4 4/4] seccomp: add support for passing fds via USER_NOTIF Tycho Andersen
2018-06-21 23:34 ` Jann Horn
2018-06-22 0:51 ` Tycho Andersen
2018-06-22 16:23 ` Jann Horn
2018-06-22 18:21 ` Andy Lutomirski
2018-08-07 2:44 ` [PATCH v4 0/4] seccomp trap to userspace Tycho Andersen
2018-08-07 2:57 ` Andy Lutomirski [this message]
2018-08-07 3:30 ` Christian Brauner
2018-08-07 4:19 ` Andy Lutomirski
2018-08-07 12:23 ` Christian Brauner
2018-08-07 14:34 ` James Bottomley
2018-08-10 0:31 ` Dinesh Subhraveti
[not found] ` <CAP4sa4+rODVahad2hW-L3h7k6fkfGBsoCfDfBVuMwp3Aaie2KA@mail.gmail.com>
2018-08-11 2:32 ` 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=62CE9671-DECD-415B-8F57-9FCCE7922990@amacapital.net \
--to=luto@amacapital.net \
--cc=christian.brauner@ubuntu.com \
--cc=containers@lists.linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=keescook@chromium.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@tobin.cc \
--cc=oleg@redhat.com \
--cc=serge@hallyn.com \
--cc=suda.akihiro@lab.ntt.co.jp \
--cc=tycho@tycho.ws \
--cc=tyhicks@canonical.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;
as well as URLs for NNTP newsgroup(s).