* Arjan van de Ven <[email protected]> wrote:
> On Tue, 2006-07-04 at 07:54 -0700, Daniel Walker wrote:
> > I got this during boot. I booted the same kernel several times, and only
> > saw it once. The kernel was 2.6.17-mm5 .
> >
> > Daniel
> >
> >
> > =========================
> > [ BUG: held lock freed! ]
> > -------------------------
> > swapper/1 is freeing memory f73a8580-f73a867f, with a lock still held there!
> > 2 locks held by swapper/1:
> > #0: (&shost->scan_mutex){--..}, at: [<c0419098>] mutex_lock+0x8/0x10
> > #1: (&eq->sysfs_lock){--..}, at: [<c0419098>] mutex_lock+0x8/0x10
>
> blargh.. it'd be more useful if lockdep actually printed which lock it
> is that it thinks is about to get freed.....
i think it's eq->sysfs_lock that is being freed here.
> this patch ought to make it do that; could you at least add this to
> your kernel?
>
> Ingo, is this the right approach?
yeah, that's OK.
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
