linux-kernel - Re: [PATCH -v5 12/17] x86/kprobes: Fix ordering

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20191114154255.GR4114@hirez.programming.kicks-ass.net>
Date:   Thu, 14 Nov 2019 16:42:55 +0100
From:   Peter Zijlstra <peterz@...radead.org>
To:     Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Cc:     paulmck <paulmck@...nel.org>, x86 <x86@...nel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        rostedt <rostedt@...dmis.org>,
        Masami Hiramatsu <mhiramat@...nel.org>,
        bristot <bristot@...hat.com>, jbaron <jbaron@...mai.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...nel.org>, Nadav Amit <namit@...are.com>,
        "H. Peter Anvin" <hpa@...or.com>,
        Andy Lutomirski <luto@...nel.org>,
        Ard Biesheuvel <ard.biesheuvel@...aro.org>,
        Josh Poimboeuf <jpoimboe@...hat.com>,
        Jessica Yu <jeyu@...nel.org>,
        Alexei Starovoitov <alexei.starovoitov@...il.com>
Subject: Re: [PATCH -v5 12/17] x86/kprobes: Fix ordering

On Thu, Nov 14, 2019 at 10:30:01AM -0500, Mathieu Desnoyers wrote:
> ----- On Nov 14, 2019, at 10:28 AM, Peter Zijlstra peterz@...radead.org wrote:

> > I don't think that is needed. As per the patch under discussion, we
> > unconditionally need that IPI-sync (even for !optimized) but we only
> > need the synchonize_rcu_tasks() thing for optimized kprobes.
> > 
> > Also, they really do two different things. Lets not tie them together.
> 
> I'm fine with this approach, I just thought it would be good to consider
> the alternative.

Fair enough; I also just remembered we use synchronize_rcu_tasks() in
scenarios where we don't need to IPI-sync, for instrance when freeing
ftrace trampolines. There we just want to make sure nothing is still
preempted inside the trampoline when we free it -- which would be BAD
:-)