lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <CALCETrXqDi24EPn79X9SXuz+5sYGZBF3yCRzb8PwdL=YbxVujw@mail.gmail.com> Date: Tue, 20 Oct 2015 18:42:52 -0700 From: Andy Lutomirski <luto@...capital.net> To: Chris Metcalf <cmetcalf@...hip.com> Cc: Steven Rostedt <rostedt@...dmis.org>, Gilad Ben Yossef <giladb@...hip.com>, Ingo Molnar <mingo@...nel.org>, Peter Zijlstra <peterz@...radead.org>, Andrew Morton <akpm@...ux-foundation.org>, Rik van Riel <riel@...hat.com>, Tejun Heo <tj@...nel.org>, Frederic Weisbecker <fweisbec@...il.com>, Thomas Gleixner <tglx@...utronix.de>, "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>, Christoph Lameter <cl@...ux.com>, Viresh Kumar <viresh.kumar@...aro.org>, Catalin Marinas <catalin.marinas@....com>, Will Deacon <will.deacon@....com>, "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>, Linux API <linux-api@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH v8 06/14] task_isolation: provide strict mode configurable signal On Tue, Oct 20, 2015 at 6:30 PM, Chris Metcalf <cmetcalf@...hip.com> wrote: > On 10/20/2015 8:56 PM, Steven Rostedt wrote: >> >> On Tue, 20 Oct 2015 16:36:04 -0400 >> Chris Metcalf <cmetcalf@...hip.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. > ...which has the odd side effect that sending a non-fatal signal from another process will cause the strict process to enter the kernel and receive an extra signal. I still dislike this thing. It seems like a debugging feature being implemented using signals instead of existing APIs. I *still* don't see why perf can't be used to accomplish your goal. --Andy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists