On 06/01/2013 05:00 PM, Eric Sandeen wrote: > And therein lies the unknown magic. > > Again, trinity's job is to try to corrupt the kernel by fuzzing syscalls. We've had "xfs bug reports" after running trinity as well... and all indications are that xfs is the victim, not the root cause. > > It could be a filesystem bug, or just as easily some other bug in a syscall that allowed trinity to corrupt memory. > > I do not think these bug reports are actionable until you can figure out how to narrow down the trinity operations that cause the problem. ok, I'm really trying to get a scenario without trinity. I'm convinced that such a scenario does exist, just because kernel 3.9.4 does not run into those issue whereas 3.10 does. -- MfG/Sincerely Toralf Förster pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3 -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
