On Mon, 19 Mar 2012, Pablo Neira Ayuso wrote: > On Sun, Mar 18, 2012 at 10:52:55PM +0200, Sasha Levin wrote: > > On Sun, Mar 18, 2012 at 4:19 PM, Pablo Neira Ayuso <pablo@xxxxxxxxxxxxx> wrote: > > > On Sun, Mar 18, 2012 at 12:55:13PM +0200, Sasha Levin wrote: > > >> Hi all, > > >> > > >> I got the following spew after fuzzing using trinity on a KVM tools > > >> guest, using the latest linux-next. > > >> > > >> It reminds me a lot of https://lkml.org/lkml/2012/3/14/375 and > > >> https://lkml.org/lkml/2012/1/14/45 > > > > > > You mention neither Linux kernel version nor the way you trigger this. > > > > > > With that little information it's really hard to really know. > > > > Hum? I've mentioned it happened with "the latest linux-next" (which is > > currently two days old), and using the trinity fuzzer - which means > > that I don't have a specific method to reproduce the problem. > > Sorry, I should not read my email diagonally, really. > > Looking at the trace, I'd point to some problem in the slub memory > allocator. Please, correct me if I'm wrong. > > Christoph? This is sually something causing memory corruption. Please enable debugging to get backtrace that help to debutg this. CONFIG_SLUB_DEBUG_ON will do the trick or passing "slub_debug" on the kernel command line. -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
