Re: [PATCH] seccomp: Only dump core when single-threaded

2017-02-22 Thread Kees Cook
On Wed, Feb 22, 2017 at 3:35 PM, Andrei Vagin 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/

Re: [PATCH] seccomp: Only dump core when single-threaded

2017-02-22 Thread Andrei Vagin
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

Re: [PATCH] seccomp: Only dump core when single-threaded

2017-02-14 Thread James Morris
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 -- James Morris

Re: [PATCH] seccomp: Only dump core when single-threaded

2017-02-14 Thread Kees Cook
On Mon, Feb 13, 2017 at 10:37 PM, Andrei Vagin wrote: > On Tue, Feb 07, 2017 at 03:18:51PM -0800, Kees Cook wrote: >> The SECCOMP_RET_KILL filter return code has always killed the current >> thread, not the entire process. Changing this as a side-effect of dumping >> core isn't a safe thing to do

Re: [PATCH] seccomp: Only dump core when single-threaded

2017-02-13 Thread Andrei Vagin
On Tue, Feb 07, 2017 at 03:18:51PM -0800, Kees Cook wrote: > The SECCOMP_RET_KILL filter return code has always killed the current > thread, not the entire process. Changing this as a side-effect of dumping > core isn't a safe thing to do (a few test suites have already flagged this > behavioral ch