mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: James Morris <jmorris@namei.org>
Cc: linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org, Jann Horn <jann@thejh.net>,
	Andy Lutomirski <luto@amacapital.net>
Subject: [PULL] seccomp update (next)
Date: Tue, 5 Jan 2016 15:40:25 -0800	[thread overview]
Message-ID: <20160105234025.GA16198@www.outflux.net> (raw)

Hi,

Please pull these seccomp changes for next.

Thanks!

-Kees

The following changes since commit aa98b942cbf305cf2abe5dc3aff11f579c7d7fdc:

  Merge branch 'smack-for-4.5' of https://github.com/cschaufler/smack-next into next (2015-12-26 16:11:13 +1100)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/seccomp-next

for you to fetch changes up to d96c17fcc58f8a486fea74d6f96a4a9407109d97:

  seccomp: always propagate NO_NEW_PRIVS on tsync (2016-01-05 15:35:41 -0800)

----------------------------------------------------------------
Fix NNP when already under root-created filter

----------------------------------------------------------------
Jann Horn (1):
      seccomp: always propagate NO_NEW_PRIVS on tsync

 kernel/seccomp.c | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

-- 
Kees Cook
Chrome OS & Brillo Security

             reply	other threads:[~2016-01-05 23:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-05 23:40 Kees Cook [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-07-07 17:59 Kees Cook
2016-07-07 23:47 ` James Morris
2016-06-14 17:57 Kees Cook
2016-06-17  7:15 ` James Morris
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
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=20160105234025.GA16198@www.outflux.net \
    --to=keescook@chromium.org \
    --cc=jann@thejh.net \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@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
all inboxes | Powered by JetHome®