lkml.org 
[lkml]   [2007]   [Mar]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: lockdep question (was Re: IPoIB caused a kernel: BUG: softlockup detected on CPU#0!)
> Quoting Ingo Molnar <mingo@elte.hu>:
> Subject: Re: lockdep question (was Re: IPoIB caused a kernel: BUG: softlockup detected on CPU#0!)
>
>
> * Michael S. Tsirkin <mst@mellanox.co.il> wrote:
>
> > > So either there are other sites that instanciate those objects and
> > > forget about the lock init, or the object is corrupted (use after free?)
> >
> > OK, thanks for the hint. So I added this:
>
> > And sure enough it triggers:
> >
> > [ 858.503010] ipoib_neigh_destructor lock c0687880 wrong type 772 !!!!!!!!!!
>
> 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.


--
MST
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2007-03-12 14:31    [W:0.034 / U:0.096 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site