On Tue, 20 Oct 2015 21:30:36 -0400 Chris Metcalf <cmetc...@ezchip.com> wrote:
> On 10/20/2015 8:56 PM, Steven Rostedt wrote: > > On Tue, 20 Oct 2015 16:36:04 -0400 > > Chris Metcalf <cmetc...@ezchip.com> wrote: > > > >> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
