From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Rostedt Subject: Re: [PATCH v8 06/14] task_isolation: provide strict mode configurable signal Date: Tue, 20 Oct 2015 20:56:10 -0400 Message-ID: <20151020205610.51b3d742@grimm.local.home> References: <1445373372-6567-1-git-send-email-cmetcalf@ezchip.com> <1445373372-6567-7-git-send-email-cmetcalf@ezchip.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1445373372-6567-7-git-send-email-cmetcalf@ezchip.com> Sender: linux-doc-owner@vger.kernel.org To: Chris Metcalf Cc: Gilad Ben Yossef , Ingo Molnar , Peter Zijlstra , Andrew Morton , Rik van Riel , Tejun Heo , Frederic Weisbecker , Thomas Gleixner , "Paul E. McKenney" , Christoph Lameter , Viresh Kumar , Catalin Marinas , Will Deacon , Andy Lutomirski , linux-doc@vger.kernel.org, linux-api@vger.kernel.org, linux-kernel@vger.kernel.org List-Id: linux-api@vger.kernel.org On Tue, 20 Oct 2015 16:36:04 -0400 Chris Metcalf 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. -- Steve