From: James Morris <james.l.morris@oracle.com>
To: Kees Cook <keescook@chromium.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, "Mickaël Salaün" <mic@digikod.net>
Subject: Re: [GIT PULL] seccomp fixes for v4.8-rc6
Date: Thu, 8 Sep 2016 14:31:04 +1000 [thread overview]
Message-ID: <68ceda06-ba1d-7f91-6416-791ed7832c4a@oracle.com> (raw)
In-Reply-To: <20160907162900.GA30378@www.outflux.net>
Actually I asked if you could send them to me...
On 08/09/16 02:29, Kees Cook wrote:
> Hi,
>
> Please pull these seccomp fixes for v4.8-rc6. These got accidentally
> put in James's -next tree, but they're needed for v4.8. He asked me to
> forward them directly to you.
>
> Thanks!
>
> -Kees
>
> The following changes since commit d060e0f603a4156087813d221d818bb39ec91429:
>
> Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dledford/rdma (2016-09-06 12:33:12 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/seccomp-v4.8-rc6
>
> for you to fetch changes up to 4fadd04d504a82f7f1fdeaddc144a9c396d1285e:
>
> seccomp: Remove 2-phase API documentation (2016-09-07 09:25:05 -0700)
>
> ----------------------------------------------------------------
> - Fix UM seccomp vs ptrace, after reordering landed.
>
> ----------------------------------------------------------------
> Mickaël Salaün (3):
> um/ptrace: Fix the syscall_trace_leave call
> um/ptrace: Fix the syscall number update after a ptrace
> seccomp: Remove 2-phase API documentation
>
> arch/Kconfig | 11 -----------
> arch/um/kernel/skas/syscall.c | 10 +++-------
> arch/x86/um/ptrace_32.c | 3 +++
> arch/x86/um/ptrace_64.c | 4 ++++
> 4 files changed, 10 insertions(+), 18 deletions(-)
>
next prev parent reply other threads:[~2016-09-08 4:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 16:29 Kees Cook
2016-09-08 4:31 ` James Morris [this message]
2016-09-08 15:53 ` Kees Cook
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=68ceda06-ba1d-7f91-6416-791ed7832c4a@oracle.com \
--to=james.l.morris@oracle.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mic@digikod.net \
--cc=torvalds@linux-foundation.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®