From: Kees Cook <keescook@chromium.org>
To: Andrei Vagin <avagin@virtuozzo.com>
Cc: James Morris <jmorris@namei.org>,
James Morris <james.l.morris@oracle.com>,
Mike Frysinger <vapier@gentoo.org>,
Paul Moore <paul@paul-moore.com>,
Tyler Hicks <tyhicks@canonical.com>,
Andy Lutomirski <luto@amacapital.net>,
Will Drewry <wad@chromium.org>,
linux-security-module <linux-security-module@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] seccomp: Only dump core when single-threaded
Date: Wed, 22 Feb 2017 16:01:32 -0800 [thread overview]
Message-ID: <CAGXu5jLS+=PPqFTcf4qyVNU7_4StXnb7Et2vWqDKK94+u4+-ig@mail.gmail.com> (raw)
In-Reply-To: <20170222233527.GA30177@outlook.office365.com>
On Wed, Feb 22, 2017 at 3:35 PM, Andrei Vagin <avagin@virtuozzo.com> wrote:
> On Wed, Feb 15, 2017 at 09:34:35AM +1100, James Morris wrote:
>> On Tue, 14 Feb 2017, Kees Cook wrote:
>>
>> > James, can you make sure this makes it into your -next tree for v4.11?
>>
>> Queued for next at:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git#next-queue
>
> The b25e67161c29 ("seccomp: dump core when using SECCOMP_RET_KILL") is
> in the Linus' tree, but this patch isn't there yet. And I don't see it
> event in linux-next.
>
> Do you have any plan to push it into the linus' tree?
>
> https://travis-ci.org/avagin/criu/builds/204341051
Yup, I already called James's attention to this. He just sent a pull
request with the fix.
-Kees
--
Kees Cook
Pixel Security
prev parent reply other threads:[~2017-02-23 0:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 23:18 [PATCH] seccomp: Only dump core when single-threaded Kees Cook
2017-02-14 6:37 ` Andrei Vagin
2017-02-14 19:09 ` Kees Cook
2017-02-14 22:34 ` James Morris
2017-02-22 23:35 ` Andrei Vagin
2017-02-23 0:01 ` Kees Cook [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='CAGXu5jLS+=PPqFTcf4qyVNU7_4StXnb7Et2vWqDKK94+u4+-ig@mail.gmail.com' \
--to=keescook@chromium.org \
--cc=avagin@virtuozzo.com \
--cc=james.l.morris@oracle.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=paul@paul-moore.com \
--cc=tyhicks@canonical.com \
--cc=vapier@gentoo.org \
--cc=wad@chromium.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).