From: "Serge E. Hallyn" <serge@hallyn.com>
To: David Drysdale <drysdale@google.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Andy Lutomirski <luto@amacapital.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Serge E. Hallyn" <serge@hallyn.com>
Subject: Re: RFC: fsyscall
Date: Thu, 10 Sep 2015 08:28:09 -0500 [thread overview]
Message-ID: <20150910132809.GA27602@mail.hallyn.com> (raw)
In-Reply-To: <CAHse=S-9oORtSHoNx1Hety1oC=unmWAxw_REUOLeQhaf3im_Kw@mail.gmail.com>
On Wed, Sep 09, 2015 at 06:27:06PM +0100, David Drysdale wrote:
> On Wed, Sep 9, 2015 at 1:25 AM, Eric W. Biederman <ebiederm@xmission.com> wrote:
> > Andy Lutomirski <luto@amacapital.net> writes:
> > > On Tue, Sep 8, 2015 at 4:07 PM, Eric W. Biederman <ebiederm@xmission.com> wrote:
>
> (From this perspective, the limitation that seccomp-bpf programs only
> have access to syscall arguments by-value is actually a help -- the filter
> can't look into user memory, so can't be fooled by having memory
> contents changed underneath it. Of course, if the eBPF stuff ever
> changes that we should watch out...)
Yup and I'm quite sure I've seen that raised as a reason to refuse
supporting exactly that.
next prev parent reply other threads:[~2015-09-10 13:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 22:35 RFC: fsyscall Eric W. Biederman
2015-09-08 22:55 ` Andy Lutomirski
2015-09-08 23:07 ` Eric W. Biederman
2015-09-08 23:18 ` Andy Lutomirski
2015-09-09 0:25 ` Eric W. Biederman
2015-09-09 17:27 ` David Drysdale
2015-09-09 19:33 ` Eric W. Biederman
2015-09-10 13:35 ` Serge E. Hallyn
2015-09-10 13:28 ` Serge E. Hallyn [this message]
2015-09-10 13:43 ` Serge E. Hallyn
2015-09-10 13:51 ` David Drysdale
2015-09-10 14:01 ` Serge E. Hallyn
2015-09-10 14:03 ` Serge E. Hallyn
2015-09-10 14:04 ` Serge E. Hallyn
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=20150910132809.GA27602@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=drysdale@google.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
/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