Re: lockdep question (was Re: IPoIB caused a kernel: BUG: softlockup detected on CPU#0!)

2007-03-12 Thread Michael S. Tsirkin
> Quoting Ingo Molnar <[EMAIL PROTECTED]>: > Subject: Re: lockdep question (was Re: IPoIB caused a kernel: BUG: softlockup > detected on CPU#0!) > > > * Michael S. Tsirkin <[EMAIL PROTECTED]> wrote: > > > > could you turn on CONFIG_SLAB_DEBUG as well? > > > > > > that should catch certain

Re: lockdep question (was Re: IPoIB caused a kernel: BUG: softlockup detected on CPU#0!)

2007-03-12 Thread Ingo Molnar
* 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

Re: lockdep question (was Re: IPoIB caused a kernel: BUG: softlockup detected on CPU#0!)

2007-03-12 Thread Michael S. Tsirkin
> Quoting Ingo Molnar <[EMAIL PROTECTED]>: > Subject: Re: lockdep question (was Re: IPoIB caused a kernel: BUG: softlockup > detected on CPU#0!) > > > * Michael S. Tsirkin <[EMAIL PROTECTED]> wrote: > > > > So either there are other sites that instanciate those objects and > > > forget about

Re: lockdep question (was Re: IPoIB caused a kernel: BUG: softlockup detected on CPU#0!)

2007-03-12 Thread Michael S. Tsirkin
Quoting Ingo Molnar [EMAIL PROTECTED]: Subject: Re: lockdep question (was Re: IPoIB caused a kernel: BUG: softlockup detected on CPU#0!) * Michael S. Tsirkin [EMAIL PROTECTED] wrote: So either there are other sites that instanciate those objects and forget about the lock init, or

Re: lockdep question (was Re: IPoIB caused a kernel: BUG: softlockup detected on CPU#0!)

2007-03-12 Thread Ingo Molnar
* 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

Re: lockdep question (was Re: IPoIB caused a kernel: BUG: softlockup detected on CPU#0!)

2007-03-12 Thread Michael S. Tsirkin
Quoting Ingo Molnar [EMAIL PROTECTED]: Subject: Re: lockdep question (was Re: IPoIB caused a kernel: BUG: softlockup detected on CPU#0!) * Michael S. Tsirkin [EMAIL PROTECTED] wrote: could you turn on CONFIG_SLAB_DEBUG as well? that should catch certain types of use-after-free

Re: lockdep question (was Re: IPoIB caused a kernel: BUG: softlockup detected on CPU#0!)

2007-03-11 Thread Ingo Molnar
* Michael S. Tsirkin <[EMAIL PROTECTED]> 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]

Re: lockdep question (was Re: IPoIB caused a kernel: BUG: softlockup detected on CPU#0!)

2007-03-11 Thread Michael S. Tsirkin
Quoting Peter Zijlstra <[EMAIL PROTECTED]>: Subject: Re: lockdep question (was Re: IPoIB caused a kernel: BUG: softlockup detected on CPU#0!) > On Sun, 2007-03-11 at 15:50 +0200, Michael S. Tsirkin wrote: > > > Quoting Roland Dreier <[EMAIL PROTECTED]>: > > > Subject: Re: IPoIB caused a kernel:

Re: lockdep question (was Re: IPoIB caused a kernel: BUG: softlockup detected on CPU#0!)

2007-03-11 Thread Michael S. Tsirkin
Quoting Peter Zijlstra [EMAIL PROTECTED]: Subject: Re: lockdep question (was Re: IPoIB caused a kernel: BUG: softlockup detected on CPU#0!) On Sun, 2007-03-11 at 15:50 +0200, Michael S. Tsirkin wrote: Quoting Roland Dreier [EMAIL PROTECTED]: Subject: Re: IPoIB caused a kernel: BUG: soft

Re: lockdep question (was Re: IPoIB caused a kernel: BUG: softlockup detected on CPU#0!)

2007-03-11 Thread Ingo Molnar
* Michael S. Tsirkin [EMAIL PROTECTED] 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]