[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180905075238.GN24124@hirez.programming.kicks-ass.net>
Date: Wed, 5 Sep 2018 09:52:38 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Jiri Kosina <jikos@...nel.org>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
Josh Poimboeuf <jpoimboe@...hat.com>,
Andrea Arcangeli <aarcange@...hat.com>,
"Woodhouse, David" <dwmw@...zon.co.uk>,
Oleg Nesterov <oleg@...hat.com>,
Tim Chen <tim.c.chen@...ux.intel.com>,
linux-kernel@...r.kernel.org, x86@...nel.org
Subject: Re: [PATCH v3 2/3] x86/speculation: apply IBPB more strictly to
avoid cross-process data leak
On Tue, Sep 04, 2018 at 04:42:02PM +0200, Jiri Kosina wrote:
> if (tsk && tsk->mm &&
> tsk->mm->context.ctx_id != last_ctx_id &&
> - get_dumpable(tsk->mm) != SUID_DUMP_USER)
> + ___ptrace_may_access(current, tsk, PTRACE_MODE_IBPB))
> indirect_branch_prediction_barrier();
See how the new (first) argument is 'current' and you could've just used
the old __ptrace_may_access().
Powered by blists - more mailing lists