Re: WARNING in tracepoint_probe_register_prio (2)

2018-03-15 Thread Jiri Olsa
On Thu, Mar 15, 2018 at 07:52:23AM -0400, Mathieu Desnoyers wrote: > - On Mar 15, 2018, at 5:19 AM, Jiri Olsa jo...@redhat.com wrote: > > > On Thu, Mar 15, 2018 at 09:31:25AM +0100, Peter Zijlstra wrote: > >> On Wed, Mar 14, 2018 at 05:37:46PM -0400, Steven Rostedt wrote: > >> > On Tue, 13 Mar

Re: WARNING in tracepoint_probe_register_prio (2)

2018-03-15 Thread Mathieu Desnoyers
- On Mar 15, 2018, at 5:19 AM, Jiri Olsa jo...@redhat.com wrote: > On Thu, Mar 15, 2018 at 09:31:25AM +0100, Peter Zijlstra wrote: >> On Wed, Mar 14, 2018 at 05:37:46PM -0400, Steven Rostedt wrote: >> > On Tue, 13 Mar 2018 11:29:51 -0400 (EDT) >> > Mathieu Desnoyers wrote: >> > >> > > Here i

Re: WARNING in tracepoint_probe_register_prio (2)

2018-03-15 Thread Jiri Olsa
On Thu, Mar 15, 2018 at 09:31:25AM +0100, Peter Zijlstra wrote: > On Wed, Mar 14, 2018 at 05:37:46PM -0400, Steven Rostedt wrote: > > On Tue, 13 Mar 2018 11:29:51 -0400 (EDT) > > Mathieu Desnoyers wrote: > > > > > Here is a WARN_ON() splat in tracepoint.c, which I suspect is caused > > > by perf

Re: WARNING in tracepoint_probe_register_prio (2)

2018-03-15 Thread Peter Zijlstra
On Wed, Mar 14, 2018 at 05:37:46PM -0400, Steven Rostedt wrote: > On Tue, 13 Mar 2018 11:29:51 -0400 (EDT) > Mathieu Desnoyers wrote: > > > Here is a WARN_ON() splat in tracepoint.c, which I suspect is caused > > by perf trying to register the same probe twice to the tracepoint API. > > We got an

Re: WARNING in tracepoint_probe_register_prio (2)

2018-03-14 Thread Steven Rostedt
On Tue, 13 Mar 2018 11:29:51 -0400 (EDT) Mathieu Desnoyers wrote: > Here is a WARN_ON() splat in tracepoint.c, which I suspect is caused > by perf trying to register the same probe twice to the tracepoint API. > We got another splat on unregister too, which I will forward in a > separate email. >

Re: WARNING in tracepoint_probe_register_prio (2)

2018-03-13 Thread Mathieu Desnoyers
- On Mar 12, 2018, at 9:59 PM, syzbot syzbot+9c0d616860575a731...@syzkaller.appspotmail.com wrote: > Hello, > > syzbot hit the following crash on bpf-next commit > 6d8cb045cde681e64a5ed80a2ab70be831a7f9b0 (Fri Mar 9 07:46:33 2018 +) > bpf: comment why dots in filenames under BPF virtual