From: James Morris <james.l.morris@oracle.com>
To: Kees Cook <keescook@chromium.org>
Cc: linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
Tycho Andersen <tycho@docker.com>
Subject: Re: [GIT PULL] seccomp updates for next
Date: Wed, 29 Nov 2017 12:55:25 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1711291254380.29347@localhost> (raw)
In-Reply-To: <20171129003819.GA30686@beast>
On Tue, 28 Nov 2017, Kees Cook wrote:
> Hi James,
>
> Please pull these seccomp changes for next. This implements an interface
> for examining seccomp filter metadata when using CRIU.
>
Applied to next-testing and next-seccomp at:
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git
--
James Morris
<james.l.morris@oracle.com>
WARNING: multiple messages have this Message-ID (diff)
From: james.l.morris@oracle.com (James Morris)
To: linux-security-module@vger.kernel.org
Subject: [GIT PULL] seccomp updates for next
Date: Wed, 29 Nov 2017 12:55:25 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1711291254380.29347@localhost> (raw)
In-Reply-To: <20171129003819.GA30686@beast>
On Tue, 28 Nov 2017, Kees Cook wrote:
> Hi James,
>
> Please pull these seccomp changes for next. This implements an interface
> for examining seccomp filter metadata when using CRIU.
>
Applied to next-testing and next-seccomp at:
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git
--
James Morris
<james.l.morris@oracle.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-11-29 1:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 0:38 [GIT PULL] seccomp updates for next Kees Cook
2017-11-29 0:38 ` Kees Cook
2017-11-29 1:55 ` James Morris [this message]
2017-11-29 1:55 ` James Morris
-- strict thread matches above, loose matches on Subject: below --
2018-12-12 23:16 Kees Cook
2018-12-13 0:08 ` James Morris
2017-08-15 22:03 Kees Cook
2017-08-15 22:03 ` Kees Cook
2017-08-16 2:33 ` James Morris
2017-08-16 2:33 ` James Morris
2017-06-26 17:02 Kees Cook
2017-06-26 17:02 ` Kees Cook
2017-06-27 3:27 ` James Morris
2017-06-27 3:27 ` 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=alpine.LFD.2.20.1711291254380.29347@localhost \
--to=james.l.morris@oracle.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=tycho@docker.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.