Re: [PATCH v8 06/14] task_isolation: provide strict mode configurable signal

On Tue, 20 Oct 2015 21:30:36 -0400
Chris Metcalf [off-list ref] wrote:

On 10/20/2015 8:56 PM, Steven Rostedt wrote:

quoted

On Tue, 20 Oct 2015 16:36:04 -0400
Chris Metcalf [off-list ref] wrote:

quoted

Allow userspace to override the default SIGKILL delivered
when a task_isolation process in STRICT mode does a syscall
or otherwise synchronously enters the kernel.

Is this really a good idea? This means that there's no way to terminate
a task in this mode, even if it goes astray.

It doesn't map SIGKILL to some other signal unconditionally.  It just allows
the "hey, you broke the STRICT contract and entered the kernel" signal
to be something besides the default SIGKILL.

Ah, I misread the change log. Now looking at the actual code, it makes
sense. Sorry for the noise ;-)

-- Steve