[PULL] seccomp update (4.5-rc2)

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>
Subject: [PULL] seccomp update (4.5-rc2)
Date: Wed, 27 Jan 2016 07:43:17 -0800	[thread overview]
Message-ID: <20160127154317.GA4243@www.outflux.net> (raw)

Hi,

Please pull these seccomp changes for 4.5-rc2. It seems my earlier request
got lost?
http://www.mail-archive.com/linux-security-module@vger.kernel.org/msg04067.html

Thanks!

-Kees

The following changes since commit 607259e17b37017e9ec0249a8b0a7d8b76b572aa:

  Merge branch 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity into ra-next (2016-01-10 21:52:17 +1100)

are available in the git repository at:

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

for you to fetch changes up to 103502a35cfce0710909da874f092cb44823ca03:

  seccomp: always propagate NO_NEW_PRIVS on tsync (2016-01-27 07:38:25 -0800)

----------------------------------------------------------------
Fix NNP vs TSYNC bug when process under root-added filter already

----------------------------------------------------------------
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-27 15:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20160127154317.GA4243@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 \
    /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®