linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
To: Kees Cook <keescook@chromium.org>
Cc: linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org, Andy Lutomirski <luto@kernel.org>
Subject: Re: [PULL] seccomp update (next)
Date: Fri, 17 Jun 2016 17:15:02 +1000 (AEST)	[thread overview]
Message-ID: <alpine.LRH.2.20.1606171714470.31596@namei.org> (raw)
In-Reply-To: <20160614175729.GA20816@www.outflux.net>

On Tue, 14 Jun 2016, Kees Cook wrote:

> Hi,
> 
> Please pull these seccomp changes for next. These have been tested by
> myself and Andy, and close a long-standing issue with seccomp where tracers
> could change the syscall out from under seccomp.

Pulled to security -next.


-- 
James Morris
<jmorris@namei.org>

  reply	other threads:[~2016-06-17  7:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-14 17:57 [PULL] seccomp update (next) Kees Cook
2016-06-17  7:15 ` James Morris [this message]
2016-06-17 18:55   ` Andy Lutomirski
2016-06-18  7:02     ` Kees Cook
2016-06-18 10:21       ` Andy Lutomirski
2016-06-19 22:45         ` Andy Lutomirski
  -- strict thread matches above, loose matches on Subject: below --
2016-07-07 17:59 Kees Cook
2016-07-07 23:47 ` James Morris
2016-01-05 23:40 Kees Cook
2015-07-15 18:56 Kees Cook
2015-07-20  6:58 ` James Morris
2014-11-25 19:43 Kees Cook
2014-11-26 13:23 ` James Morris
2014-11-26 21:46   ` Stephen Rothwell
2014-11-26 21:59     ` Kees Cook
2014-11-27 23:37       ` James Morris
2014-12-01 20:34         ` Kees Cook
2014-12-01 22:56           ` James Morris
2014-12-01 23:06             ` Kees Cook
2014-12-02  7:56               ` James Morris

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=alpine.LRH.2.20.1606171714470.31596@namei.org \
    --to=jmorris@namei.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=luto@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;
as well as URLs for NNTP newsgroup(s).