From: James Morris <jmorris@namei.org>
To: Kees Cook <keescook@chromium.org>
Cc: Mike Frysinger <vapier@gentoo.org>,
James Morris <james.l.morris@oracle.com>,
LKML <linux-kernel@vger.kernel.org>,
Andy Lutomirski <luto@amacapital.net>,
Will Drewry <wad@chromium.org>,
Mike Frysinger <vapier@chromium.org>
Subject: Re: [PATCH] seccomp: dump core when using SECCOMP_RET_KILL
Date: Mon, 23 Jan 2017 09:10:25 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LRH.2.20.1701230909540.27432@namei.org> (raw)
In-Reply-To: <CAGXu5jK3Vp9eXZngaK+HosF8Vs_iQEgdSxFXz0w7F4if1qdNFg@mail.gmail.com>
On Fri, 20 Jan 2017, Kees Cook wrote:
> Yup, I think this is fine. The additional kernel code executed before
> the do_exit() is relatively limited, and is equivalent to leaving
> kill(self, SIGSEGV) exposed in a seccomp filter. Setting an RLIMIT is
> also sufficient to block the core generation, so really paranoid
> environments can still do that.
>
> The forwarded ack stands:
>
> Acked-by: Kees Cook <keescook@chromium.org>
>
> James, can you add this to your tree?
Mike, please resend the patch, I don't have it.
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2017-01-22 22:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 4:28 Mike Frysinger
2017-01-20 20:37 ` Kees Cook
2017-01-22 22:10 ` James Morris [this message]
2017-01-23 7:37 ` Mike Frysinger
2017-01-23 10:23 ` James Morris
2017-01-25 0:53 ` Andrei Vagin
2017-01-25 1:42 ` Mike Frysinger
2017-01-25 20:05 ` Kees Cook
2017-01-27 21:48 ` Kees Cook
2017-01-28 14:35 ` Paul Moore
2017-01-31 21:47 ` Andrei Vagin
2017-01-31 21:59 ` Andy Lutomirski
2017-02-01 0:18 ` 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=alpine.LRH.2.20.1701230909540.27432@namei.org \
--to=jmorris@namei.org \
--cc=james.l.morris@oracle.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=vapier@chromium.org \
--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
all inboxes | Powered by JetHome®