On Thu, 24 Oct 2013, Vince Weaver wrote: > after a month of trying I finally got a small test-case out of my > perf_fuzzer suite that triggers a system lockup with just one syscall. > > Attached is the code that triggers it.
And it turns out you can only trigger this specific problem if advanced ftrace options are enabled. CONFIG_KPROBES_ON_FTRACE=y CONFIG_FUNCTION_TRACER=y CONFIG_FUNCTION_GRAPH_TRACER=y CONFIG_STACK_TRACER=y CONFIG_DYNAMIC_FTRACE=y CONFIG_DYNAMIC_FTRACE_WITH_REGS=y CONFIG_FUNCTION_PROFILER=y CONFIG_FTRACE_MCOUNT_RECORD=y Urgh, I had turned those on to try to debug something and forgot to disable. I feel like I saw this problem before I had those enabled so I guess I have to start from scratch fuzzing to see if I can get a more generally reproducible trace. Vince -- 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/
