Re: perf: fuzzer gets CPU stuck in perf_callchain()

2015-02-23 Thread Vince Weaver
On Thu, 19 Feb 2015, Peter Zijlstra wrote: > On Thu, Feb 19, 2015 at 11:54:40AM -0500, Vince Weaver wrote: > > > [ 7938.802139] [] perf_tp_event+0xc4/0x210 > > [ 7938.861174] [] perf_trace_lock+0x12a/0x160 > > [ 7938.882197] [] lock_release+0x130/0x260 > > [ 7938.888754] [] _raw_spin_unlock_i

Re: perf: fuzzer gets CPU stuck in perf_callchain()

2015-02-19 Thread Vince Weaver
On Thu, 19 Feb 2015, Vince Weaver wrote: > I have to take that back, it turns out the Cortex-A9 machine was wedged > for over a day, I just hadn't noticed because it hadn't dumped any kind > of message about the problem. Hmm. This turns out to be the find_get_context() bug that has been fixed i

Re: perf: fuzzer gets CPU stuck in perf_callchain()

2015-02-19 Thread Vince Weaver
On Thu, 19 Feb 2015, Vince Weaver wrote: > I also have a core2 and a Cortex-A9 machine fuzzing > away and they've been at it a week now without turning up anything. I have to take that back, it turns out the Cortex-A9 machine was wedged for over a day, I just hadn't noticed because it hadn't du

Re: perf: fuzzer gets CPU stuck in perf_callchain()

2015-02-19 Thread Peter Zijlstra
On Thu, Feb 19, 2015 at 11:54:40AM -0500, Vince Weaver wrote: > [ 7938.802139] [] perf_tp_event+0xc4/0x210 > [ 7938.861174] [] perf_trace_lock+0x12a/0x160 > [ 7938.882197] [] lock_release+0x130/0x260 > [ 7938.888754] [] _raw_spin_unlock_irqrestore+0x24/0x40 > [ 7938.896510] [] do_send_sig_inf

Re: perf: fuzzer gets CPU stuck in perf_callchain()

2015-02-19 Thread Vince Weaver
On Thu, 19 Feb 2015, Peter Zijlstra wrote: > On Thu, Feb 19, 2015 at 11:54:40AM -0500, Vince Weaver wrote: > > > > Another bug found by the perf_fuzzer(). I think this one is different > > than the one I sent the other day, it looks like something is going > > very wrong in perf_callchain(). > >

Re: perf: fuzzer gets CPU stuck in perf_callchain()

2015-02-19 Thread Peter Zijlstra
On Thu, Feb 19, 2015 at 11:54:40AM -0500, Vince Weaver wrote: > > Another bug found by the perf_fuzzer(). I think this one is different > than the one I sent the other day, it looks like something is going > very wrong in perf_callchain(). > > This one is reasonably reproducible, if there's any