On 09/10/2014 09:18 AM, Vince Weaver wrote: > 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.
Could this be http://permalink.gmane.org/gmane.linux.kernel/1779436 which I saw couple days ago? Thanks, Sasha -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
