linux-kernel - Re: [PATCH v4 20/23] [RFC] kprobes: Remove task scan for updating kretprobe

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]

Date:   Sat, 29 Aug 2020 01:01:35 +0900
From:   Masami Hiramatsu <mhiramat@...nel.org>
To:     peterz@...radead.org
Cc:     linux-kernel@...r.kernel.org, Eddy_Wu@...ndmicro.com,
        x86@...nel.org, davem@...emloft.net, rostedt@...dmis.org,
        naveen.n.rao@...ux.ibm.com, anil.s.keshavamurthy@...el.com,
        linux-arch@...r.kernel.org, cameron@...dycamel.com,
        oleg@...hat.com, will@...nel.org, paulmck@...nel.org
Subject: Re: [PATCH v4 20/23] [RFC] kprobes: Remove task scan for updating
 kretprobe_instance

On Fri, 28 Aug 2020 17:18:06 +0200
peterz@...radead.org wrote:

> On Sat, Aug 29, 2020 at 12:10:10AM +0900, Masami Hiramatsu wrote:
> > On Fri, 28 Aug 2020 14:52:36 +0200
> > peterz@...radead.org wrote:
> 
> > > >  	synchronize_rcu();
> > > 
> > > This one might help, this means we can do rcu_read_lock() around
> > > get_kretprobe() and it's usage. Can we call rp->handler() under RCU?
> > 
> > Yes, as I said above, the get_kretprobe() (and kretprobe handler) must be
> > called under preempt-disabled.
> 
> Then we don't need the ordering; we'll need READ_ONCE() (or
> rcu_derefernce()) to make sure the address dependency works on Alpha.
> And a comment/assertion that explains this might not go amiss in
> get_kretprobe().


OK, I'll rewrite it with READ_ONCE() and rcu_read_lock_any_held().

Thank you,

-- 
Masami Hiramatsu <mhiramat@...nel.org>