[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181019200227.GC31016@hirez.programming.kicks-ass.net>
Date: Fri, 19 Oct 2018 22:02:27 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Tim Chen <tim.c.chen@...ux.intel.com>
Cc: Jiri Kosina <jikos@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Tom Lendacky <thomas.lendacky@....com>,
Ingo Molnar <mingo@...hat.com>,
Josh Poimboeuf <jpoimboe@...hat.com>,
Andrea Arcangeli <aarcange@...hat.com>,
David Woodhouse <dwmw@...zon.co.uk>,
Andi Kleen <ak@...ux.intel.com>,
Dave Hansen <dave.hansen@...el.com>,
Casey Schaufler <casey.schaufler@...el.com>,
Asit Mallick <asit.k.mallick@...el.com>,
Arjan van de Ven <arjan@...ux.intel.com>,
Jon Masters <jcm@...hat.com>, linux-kernel@...r.kernel.org,
x86@...nel.org
Subject: Re: [Patch v3 06/13] mm: Pass task instead of task->mm as argument
to set_dumpable
On Wed, Oct 17, 2018 at 10:59:34AM -0700, Tim Chen wrote:
> Change the argument to set_dumpable from task->mm to task. This allows us
> to later add hooks to modify a task's property according to whether it is
> a non-dumpable task. Non dumpable tasks demand a higher level of security.
> Changes the dumpable value from in to unsigned int as negative number is
> not allowed.
Per task dumpable doesn't make any kind of sense. Dumpable is about
coredumps, that's an mm property.
If you want to introduce other (per task) state; give that a new name
and check for that explicitly. Don't create confusion like this.
Powered by blists - more mailing lists