linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: James Morris <jmorris@namei.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"Mickaël Salaün" <mic@digikod.net>,
	"Ricky Zhou" <rickyz@chromium.org>,
	linux-security-module <linux-security-module@vger.kernel.org>
Subject: Re: [GIT PULL] seccomp fixes for v4.9-rc4
Date: Tue, 1 Nov 2016 20:07:45 -0600	[thread overview]
Message-ID: <CAGXu5jKYBnjkTpuO9xeJw2gRya=7V3x-R53MBYG8x_7jrK5m=g@mail.gmail.com> (raw)
In-Reply-To: <alpine.LRH.2.20.1611020942030.24564@namei.org>

On Tue, Nov 1, 2016 at 4:43 PM, James Morris <jmorris@namei.org> wrote:
> On Tue, 1 Nov 2016, Kees Cook wrote:
>
>> Hi,
>>
>> Please pull these seccomp fixes for v4.9-rc4.
>
>> ----------------------------------------------------------------
>> - fix function prototype documentation
>> - fix samples to include NNP setting
>> - fix samples to avoid rule truncation
>> - fix samples hostprogs variable in Makefile
>>
>> ----------------------------------------------------------------
>
> These fixes don't seem very critical, and Linus was talking yesterday at
> KS about too much churn in the -rc series with non-critical fixes.
>
> How about we queue this up for 4.10?

Okay, sounds good to me. Thanks!

-Kees

-- 
Kees Cook
Nexus Security

  reply	other threads:[~2016-11-02  2:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-01 17:46 [GIT PULL] seccomp fixes for v4.9-rc4 Kees Cook
2016-11-01 22:43 ` James Morris
2016-11-02  2:07   ` Kees Cook [this message]
2016-11-04 16:35     ` 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='CAGXu5jKYBnjkTpuO9xeJw2gRya=7V3x-R53MBYG8x_7jrK5m=g@mail.gmail.com' \
    --to=keescook@chromium.org \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=mic@digikod.net \
    --cc=rickyz@chromium.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).