[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.11.1409100914410.8981@vincent-weaver-1.umelst.maine.edu>
Date: Wed, 10 Sep 2014 09:18:35 -0400 (EDT)
From: Vince Weaver <vincent.weaver@...ne.edu>
To: Peter Zijlstra <peterz@...radead.org>
cc: Vince Weaver <vincent.weaver@...ne.edu>,
linux-kernel@...r.kernel.org, Paul Mackerras <paulus@...ba.org>,
Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Steven Rostedt <rostedt@...dmis.org>
Subject: Re: perf: perf_fuzzer triggers instant reboot
On Wed, 10 Sep 2014, Peter Zijlstra wrote:
>
> Sasha reported something from his KVM based fuzzing, maybe that's the
> same. But that x86_exceptions thing is interesting, lemme go look at
> that first.
that's what got me looking at things again, the trinity reports. Though I
think those involve CPU hotplugging which my fuzzer shouldn't trigger.
I do think this is the same memory corruption/reboot bug that I reported
back in February (the thread is "perf_fuzzer compiled for x32 causes
reboot" but I wasn't able to isolate the problem then either.
Somehow something is stomping over memory with a forking workload (likely
an improper free with RCU like we've seen before) but the fact that it
causes a reboot immediately makes it *really* hard to debug this.
I'm not sure about the tracing issue, possibly it's just a side effect of
memory being corrupted by the same bug. In case it's relevant here's the
trace-cmd I was trying to use:
trace-cmd record -e raw_syscalls -p function -l '*perf*' -n 'perf_event_task_tick' -l 'x86*' -l 'intel*' -P 2807
Vince
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists