Messages in this thread | | | Date | Mon, 23 Jan 2017 09:10:25 +1100 (AEDT) | From | James Morris <> | Subject | Re: [PATCH] seccomp: dump core when using SECCOMP_RET_KILL |
| |
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>
| |