From: Alexei Starovoitov <alexei.starovoitov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Sargun Dhillon <sargun-GaZTRHToo+CzQB+pC5nmwQ@public.gmane.org>
Cc: netdev <netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linux Containers
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
Kees Cook <keescook-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
Daniel Borkmann <daniel-FeC+5ew28dpmcu3hnIyYJQ@public.gmane.org>
Subject: Re: Userspace helper design
Date: Tue, 6 Mar 2018 13:51:14 -0800 [thread overview]
Message-ID: <20180306215112.yn2ei6ypzo74hexv@ast-mbp.dhcp.thefacebook.com> (raw)
In-Reply-To: <CAMp4zn8fdMYOpemqaQ_7+KAMmnVtHzi-wz_RqG_HJh15b81SDg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Tue, Mar 06, 2018 at 01:14:30PM -0800, Sargun Dhillon wrote:
>
> So, would this verifier just ensure that no maps are accessed prior to
> the helper being called, XOR ensure that after the helper is called,
> no map values are accessed?
Nack on this design.
prev parent reply other threads:[~2018-03-06 21:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180306013448.GA6631@ircssh-2.c.rugged-nimbus-611.internal>
[not found] ` <20180306014542.me6xtmyhhkystywz@ast-mbp>
[not found] ` <CAMp4zn_c51SC5gvsk=pzTD7UCsid1DCyPhe-ScohZzrpyObu7g@mail.gmail.com>
[not found] ` <20180306015351.5swdihfrisxb7226@ast-mbp>
[not found] ` <307b9945-57d0-1178-32af-3837aaefae90@iogearbox.net>
[not found] ` <CAMp4zn-Ga08OFF34BiQ+YqcnmKYrAbNgRKbK9UkG5TfVrjLqTw@mail.gmail.com>
[not found] ` <fc4e2ea0-5bdc-a0be-c500-f55e7de8e1bd@iogearbox.net>
[not found] ` <fc4e2ea0-5bdc-a0be-c500-f55e7de8e1bd-FeC+5ew28dpmcu3hnIyYJQ@public.gmane.org>
2018-03-06 21:14 ` Userspace helper design Sargun Dhillon
[not found] ` <CAMp4zn8fdMYOpemqaQ_7+KAMmnVtHzi-wz_RqG_HJh15b81SDg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-03-06 21:51 ` Alexei Starovoitov [this message]
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=20180306215112.yn2ei6ypzo74hexv@ast-mbp.dhcp.thefacebook.com \
--to=alexei.starovoitov-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=daniel-FeC+5ew28dpmcu3hnIyYJQ@public.gmane.org \
--cc=keescook-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sargun-GaZTRHToo+CzQB+pC5nmwQ@public.gmane.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).