From: Tycho Andersen <tycho@docker.com>
To: Kees Cook <keescook@chromium.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
criu@openvz.org, Andy Lutomirski <luto@amacapital.net>,
Oleg Nesterov <oleg@redhat.com>
Subject: Re: [PATCH] ptrace, seccomp: add support for retrieving seccomp flags
Date: Tue, 19 Sep 2017 15:09:16 -0600 [thread overview]
Message-ID: <20170919210916.6r5janszdtx7eoes@smitten> (raw)
In-Reply-To: <CAGXu5j+0neV5uGm3qNmFSYodWoC3VsMEjP7JkFd5B_ksNFAvkg@mail.gmail.com>
Hi Kees,
On Tue, Sep 19, 2017 at 01:08:28PM -0700, Kees Cook wrote:
> On Tue, Sep 19, 2017 at 10:47 AM, Tycho Andersen <tycho@docker.com> wrote:
> > With the new SECCOMP_FILTER_FLAG_LOG, we need to be able to extract these
> > flags for checkpoint restore, since they describe the state of a filter.
> >
> > So, let's add PTRACE_SECCOMP_GET_FLAGS, similar to ..._GET_FILTER, which
> > returns the flags of the nth filter.
>
> Can you split this up into factoring out the nth helper, and then
> adding the new get?
>
> For naming, perhaps "GET_FILTER_FLAGS" instead of "GET_FLAGS" since
> there may be seccomp flags in the future, etc.
Sure, I'll do both of these.
> Is there any sane way to add the flags to the existing GET_FILTER?
I looked at this, and I don't think so. Unfortunately, we didn't use
any structure for the output, it's just the raw bytes of the filter
with the length used as the return value. I suppose we could append
the flags after the bytes of the filter, but that seems... very ugly
:). Let me know if you want to go that route.
Tycho
next prev parent reply other threads:[~2017-09-19 21:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 17:47 Tycho Andersen
2017-09-19 20:08 ` Kees Cook
2017-09-19 21:09 ` Tycho Andersen [this message]
2017-09-19 21:43 ` Kees Cook
2017-09-19 21:55 ` Tycho Andersen
2017-09-19 22:09 ` Kees Cook
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=20170919210916.6r5janszdtx7eoes@smitten \
--to=tycho@docker.com \
--cc=criu@openvz.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=oleg@redhat.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
all inboxes | Powered by JetHome®