From: Kees Cook <keescook@chromium.org>
To: James Morris <jmorris@namei.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Tycho Andersen <tycho@tycho.ws>,
Heiko Carstens <heiko.carstens@de.ibm.com>
Subject: Re: [GIT PULL] seccomp updates for next (part2)
Date: Mon, 17 Dec 2018 10:00:20 -0800 [thread overview]
Message-ID: <CAGXu5jKw8sZp8PjkSG+KZVaMdb3ryLPOAgRdOxBRPiZJF3PGtQ@mail.gmail.com> (raw)
In-Reply-To: <20181214162556.GA7944@beast>
On Fri, Dec 14, 2018 at 8:26 AM Kees Cook <keescook@chromium.org> wrote:
>
>
> Hi James,
>
> Please pull these seccomp fixes for -next.
>
> Thanks!
Friendly ping: James, can you pick this up for -next?
-Kees
>
> -Kees
>
> The following changes since commit fec7b6690541b8128663a13c9586b1daf42b0a6c:
>
> samples: add an example of seccomp user trap (2018-12-11 16:32:11 -0800)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/seccomp-next-part2
>
> for you to fetch changes up to 4fc96ee9085d39ceeaa7b60cd475d0a474e7062f:
>
> seccomp, s390: fix build for syscall type change (2018-12-13 16:51:01 -0800)
>
> ----------------------------------------------------------------
> seccomp fixes for sparse warnings and s390 build (Tycho)
>
> ----------------------------------------------------------------
> Tycho Andersen (2):
> seccomp: fix poor type promotion
> seccomp, s390: fix build for syscall type change
>
> arch/s390/kernel/compat_wrapper.c | 2 +-
> kernel/seccomp.c | 3 +--
> 2 files changed, 2 insertions(+), 3 deletions(-)
>
> --
> Kees Cook
--
Kees Cook
next prev parent reply other threads:[~2018-12-17 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 16:25 [GIT PULL] seccomp updates for next (part2) Kees Cook
2018-12-17 18:00 ` Kees Cook [this message]
2018-12-17 19:36 ` 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=CAGXu5jKw8sZp8PjkSG+KZVaMdb3ryLPOAgRdOxBRPiZJF3PGtQ@mail.gmail.com \
--to=keescook@chromium.org \
--cc=heiko.carstens@de.ibm.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tycho@tycho.ws \
/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).