public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tycho Andersen <tycho@tycho.ws>
To: Christian Brauner <christian@brauner.io>
Cc: Kees Cook <keescook@chromium.org>,
	linux-api@vger.kernel.org, containers@lists.linux-foundation.org,
	Akihiro Suda <suda.akihiro@lab.ntt.co.jp>,
	Oleg Nesterov <oleg@redhat.com>,
	linux-kernel@vger.kernel.org,
	"Eric W . Biederman" <ebiederm@xmission.com>,
	Christian Brauner <christian.brauner@ubuntu.com>,
	Andy Lutomirski <luto@amacapital.net>
Subject: Re: [PATCH v5 1/5] seccomp: add a return code to trap to userspace
Date: Wed, 29 Aug 2018 15:21:27 -0600	[thread overview]
Message-ID: <20180829212127.GA15213@cisco.cisco.com> (raw)
In-Reply-To: <20180829185917.zj3gqyn6qf62sx66@mailbox.org>

On Wed, Aug 29, 2018 at 08:59:18PM +0200, Christian Brauner wrote:
> On Tue, Aug 28, 2018 at 08:35:59AM -0600, Tycho Andersen wrote:
> > +Users can ``read()`` or ``poll()`` on a seccomp notification fd to receive a
> 
> You have changed this from read() to ioctl(), right?

Derp, yes. I'll re-write this bit. Thanks for the others, I'll fix
them too. It's not bike shedding if it's incorrect :)

Thanks,

Tycho

  reply	other threads:[~2018-08-29 21:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-28 14:35 [PATCH v5 0/5] seccomp trap to userspace Tycho Andersen
2018-08-28 14:35 ` [PATCH v5 1/5] seccomp: add a return code to " Tycho Andersen
2018-08-29 18:59   ` Christian Brauner
2018-08-29 21:21     ` Tycho Andersen [this message]
2018-08-28 14:36 ` [PATCH v5 2/5] seccomp: make get_nth_filter available outside of CHECKPOINT_RESTORE Tycho Andersen
2018-08-29 19:07   ` Christian Brauner
2018-08-28 14:36 ` [PATCH v5 3/5] seccomp: add a way to get a listener fd from ptrace Tycho Andersen
2018-08-28 14:36 ` [PATCH v5 4/5] seccomp: add support for passing fds via USER_NOTIF Tycho Andersen
2018-08-28 14:36 ` [PATCH v5 5/5] samples: add an example of seccomp user trap 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=20180829212127.GA15213@cisco.cisco.com \
    --to=tycho@tycho.ws \
    --cc=christian.brauner@ubuntu.com \
    --cc=christian@brauner.io \
    --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=luto@amacapital.net \
    --cc=oleg@redhat.com \
    --cc=suda.akihiro@lab.ntt.co.jp \
    /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