On Fri, Jan 24, 2014 at 10:55:56PM +0200, Tommi Rantala wrote: > Hello, > > Trinity triggered the following bug in two separate qemu virtual > machines after fuzzing v3.13-3995-g0dc3fd0 for a day or two. I have > not been running Trinity in a while, so no idea if this is a > regression or not. Probably been there a while. I noticed on Tuesday that I hadn't annotated the 'policy' argument to sched_setscheduler(). Now that it's passing sensible arguments, I'm not surprised there's some fallout if subsequent syscalls call misc scheduler functions. Dave -- To unsubscribe from this list: send the line "unsubscribe trinity" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
