Re: possible deadlock in perf_trace_destroy (2)

2018-04-21 Thread Eric Biggers
On Tue, Jan 23, 2018 at 08:37:49AM +0100, 'Dmitry Vyukov' via syzkaller-bugs wrote: > On Tue, Jan 23, 2018 at 12:19 AM, Peter Zijlstra wrote: > > On Mon, Jan 22, 2018 at 05:20:13PM -0500, Steven Rostedt wrote: > >> > >> Peter, > >> > >> Isn't this the same as what you mentioned (and had a hack pa

Re: possible deadlock in perf_trace_destroy (2)

2018-01-22 Thread Dmitry Vyukov
On Tue, Jan 23, 2018 at 12:19 AM, Peter Zijlstra wrote: > On Mon, Jan 22, 2018 at 05:20:13PM -0500, Steven Rostedt wrote: >> >> Peter, >> >> Isn't this the same as what you mentioned (and had a hack patch for) >> before? >> >> >> http://lkml.kernel.org/r/20180109133651.gb2...@hirez.programming.k

Re: possible deadlock in perf_trace_destroy (2)

2018-01-22 Thread Peter Zijlstra
On Mon, Jan 22, 2018 at 05:20:13PM -0500, Steven Rostedt wrote: > > Peter, > > Isn't this the same as what you mentioned (and had a hack patch for) > before? > > > http://lkml.kernel.org/r/20180109133651.gb2...@hirez.programming.kicks-ass.net > Looks like it. Just haven't managed to get thos

Re: possible deadlock in perf_trace_destroy (2)

2018-01-22 Thread Steven Rostedt
Peter, Isn't this the same as what you mentioned (and had a hack patch for) before? http://lkml.kernel.org/r/20180109133651.gb2...@hirez.programming.kicks-ass.net -- Steve On Mon, 22 Jan 2018 12:57:01 -0800 syzbot wrote: > syzbot has found reproducer for the following crash on > git://gi

Re: possible deadlock in perf_trace_destroy (2)

2017-11-07 Thread Dmitry Vyukov
On Tue, Nov 7, 2017 at 12:39 PM, syzbot wrote: > Hello, > > syzkaller hit the following crash on > 5a3517e009e979f21977d362212b7729c5165d92 > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw console output is