From: "H. Peter Anvin" <hpa@zytor.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Kees Cook <keescook@chromium.org>, Will Drewry <wad@chromium.org>,
Oleg Nesterov <oleg@redhat.com>, X86 ML <x86@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
linux-mips@linux-mips.org,
linux-arch <linux-arch@vger.kernel.org>,
LSM List <linux-security-module@vger.kernel.org>
Subject: Re: [RFC 5/5] x86,seccomp: Add a seccomp fastpath
Date: Wed, 11 Jun 2014 15:27:00 -0700 [thread overview]
Message-ID: <5398D7B4.5000303@zytor.com> (raw)
In-Reply-To: <CALCETrVMxkHcPXsEGtEc0Pr=Z80CzC0zWaQ9OdVdxi1CGuB4kQ@mail.gmail.com>
On 06/11/2014 03:22 PM, Andy Lutomirski wrote:
> On Wed, Jun 11, 2014 at 3:18 PM, H. Peter Anvin <hpa@zytor.com> wrote:
>> On 06/11/2014 02:56 PM, Andy Lutomirski wrote:
>>>
>>> 13ns is with the simplest nonempty filter. I hope that empty filters
>>> don't work.
>>>
>>
>> Why wouldn't they?
>
> Is it permissible to fall off the end of a BPF program? I'm getting
> EINVAL trying to install an actual empty filter. The filter I tested
> with was:
>
What I meant was that there has to be a well-defined behavior for the
program falling off the end anyway, and that that should be preserved.
I guess it is possible to require that all code paths must provably
reach a termination point.
-hpa
next prev parent reply other threads:[~2014-06-11 22:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 20:22 [RFC 0/5] Two-phase seccomp and an x86_64 fast path Andy Lutomirski
2014-06-11 20:22 ` [RFC 1/5] seccomp,x86,arm,mips,s390: Remove nr parameter from secure_computing Andy Lutomirski
2014-06-11 20:22 ` [RFC 2/5] x86_64,entry: Treat regs->ax the same in fastpath and slowpath syscalls Andy Lutomirski
2014-06-11 20:23 ` [RFC 3/5] seccomp: Refactor the filter callback and the API Andy Lutomirski
2014-06-11 20:23 ` [RFC 4/5] seccomp: Allow arch code to provide seccomp_data Andy Lutomirski
2014-06-11 20:23 ` [RFC 5/5] x86,seccomp: Add a seccomp fastpath Andy Lutomirski
2014-06-11 21:29 ` Alexei Starovoitov
2014-06-11 21:56 ` Andy Lutomirski
2014-06-11 22:18 ` H. Peter Anvin
2014-06-11 22:22 ` Andy Lutomirski
2014-06-11 22:27 ` H. Peter Anvin [this message]
2014-06-11 22:28 ` Andy Lutomirski
2014-06-11 22:32 ` Kees Cook
2014-06-13 16:29 ` Will Drewry
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=5398D7B4.5000303@zytor.com \
--to=hpa@zytor.com \
--cc=alexei.starovoitov@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-security-module@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=oleg@redhat.com \
--cc=wad@chromium.org \
--cc=x86@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 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®