Re: [PATCHv2] kretprobe: Prevent triggering kretprobe from within kprobe_flush_task

2020-05-07 Thread Jiri Olsa
On Fri, May 01, 2020 at 11:01:07AM +0900, Masami Hiramatsu wrote: > On Tue, 28 Apr 2020 23:36:27 +0200 > Jiri Olsa wrote: > > > On Fri, Apr 17, 2020 at 04:38:10PM +0900, Masami Hiramatsu wrote: > > > > SNIP > > > > > > > > > > The code within the kretprobe handler checks for probe reentrancy,

Re: [PATCHv2] kretprobe: Prevent triggering kretprobe from within kprobe_flush_task

2020-04-30 Thread Masami Hiramatsu
On Tue, 28 Apr 2020 23:36:27 +0200 Jiri Olsa wrote: > On Fri, Apr 17, 2020 at 04:38:10PM +0900, Masami Hiramatsu wrote: > > SNIP > > > > > > > The code within the kretprobe handler checks for probe reentrancy, > > > so we won't trigger any _raw_spin_lock_irqsave probe in there. > > > > > >

Re: [PATCHv2] kretprobe: Prevent triggering kretprobe from within kprobe_flush_task

2020-04-28 Thread Jiri Olsa
On Fri, Apr 17, 2020 at 04:38:10PM +0900, Masami Hiramatsu wrote: SNIP > > > > The code within the kretprobe handler checks for probe reentrancy, > > so we won't trigger any _raw_spin_lock_irqsave probe in there. > > > > The problem is in outside kprobe_flush_task, where we call: > > > >