From: James Morris <jmorris@namei.org>
To: Kees Cook <keescook@chromium.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: Tue, 18 Dec 2018 06:36:50 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LRH.2.21.1812180636390.29218@namei.org> (raw)
In-Reply-To: <CAGXu5jKw8sZp8PjkSG+KZVaMdb3ryLPOAgRdOxBRPiZJF3PGtQ@mail.gmail.com>
On Mon, 17 Dec 2018, Kees Cook wrote:
> 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?
>
Pulled to next-seccomp and next-testing.
> -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
>
>
>
>
--
James Morris
<jmorris@namei.org>
prev parent reply other threads:[~2018-12-17 19:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 16:25 Kees Cook
2018-12-17 18:00 ` Kees Cook
2018-12-17 19:36 ` James Morris [this message]
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=alpine.LRH.2.21.1812180636390.29218@namei.org \
--to=jmorris@namei.org \
--cc=heiko.carstens@de.ibm.com \
--cc=keescook@chromium.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
all inboxes | Powered by JetHome®