* Michael S. Tsirkin <[EMAIL PROTECTED]> wrote:
> > could you turn on CONFIG_SLAB_DEBUG as well?
> >
> > that should catch certain types of use-after-free accesses, and
> > lockdep will also warn if a still locked object is freed.
>
> Hmm, no, this does not look like use-after-free. I enabled
> CONFIG_SLAB_DEBUG, and I still see the same message, so the memory was
> not overwritten by slab debugger.
that's still not conclusive - the memory might not have been allocated
by slab again to detect it. Your magic-number check definitely shows
some sort of corruption going on, right?
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
