From: Kees Cook <keescook@chromium.org>
To: James Morris <james.l.morris@oracle.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Kees Cook <keescook@chromium.org>, Kyle Huey <khuey@kylehuey.com>,
Oleg Nesterov <oleg@redhat.com>,
"Robert O'Callahan" <robert@ocallahan.org>
Subject: Re: [GIT PULL] seccomp fix for v4.8-rc4
Date: Tue, 30 Aug 2016 18:28:15 -0400 [thread overview]
Message-ID: <CAGXu5jJC16haD8sNwMTBCYUapZXowJb7m8pR4Bop2LU+g-OESQ@mail.gmail.com> (raw)
In-Reply-To: <20160823193402.GA16945@www.outflux.net>
Hi James,
Are you able to forward this up to Linus, or would it be better for me
to send this to him directly?
Thanks!
-Kees
On Tue, Aug 23, 2016 at 3:34 PM, Kees Cook <keescook@chromium.org> wrote:
> Hi,
>
> Please pull this seccomp fix for v4.8-rc4.
>
> Thanks!
>
> -Kees
>
> The following changes since commit ef0e1ea8856bed6ff8394d3dfe77f2cab487ecea:
>
> Merge tag 'arc-4.8-rc4-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc (2016-08-22 17:53:02 -0500)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/seccomp-v4.8-rc4
>
> for you to fetch changes up to e72a2623bf56a94e1396940d73bf7af7b65e0ea5:
>
> seccomp: Fix tracer exit notifications during fatal signals (2016-08-23 12:23:38 -0700)
>
> ----------------------------------------------------------------
> Fix fatal signal delivery after ptrace reordering
>
> ----------------------------------------------------------------
> Kees Cook (1):
> seccomp: Fix tracer exit notifications during fatal signals
>
> kernel/seccomp.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> --
> Kees Cook
> Nexus Security
--
Kees Cook
Nexus Security
next prev parent reply other threads:[~2016-08-30 22:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 19:34 [GIT PULL] seccomp fix for v4.8-rc4 Kees Cook
2016-08-30 22:28 ` Kees Cook [this message]
2016-08-30 23:05 ` 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=CAGXu5jJC16haD8sNwMTBCYUapZXowJb7m8pR4Bop2LU+g-OESQ@mail.gmail.com \
--to=keescook@chromium.org \
--cc=james.l.morris@oracle.com \
--cc=khuey@kylehuey.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=robert@ocallahan.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).