public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Daniel Walker <dwalker@mvista.com>,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [BUG] scsi/io-elevator held lock freed.
Date: Tue, 4 Jul 2006 17:15:04 +0200	[thread overview]
Message-ID: <20060704151504.GA10779@elte.hu> (raw)
In-Reply-To: <1152026010.3109.66.camel@laptopd505.fenrus.org>


* Arjan van de Ven <arjan@infradead.org> 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

  reply	other threads:[~2006-07-04 15:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-04 14:54 [BUG] scsi/io-elevator held lock freed Daniel Walker
2006-07-04 15:13 ` Arjan van de Ven
2006-07-04 15:15   ` Ingo Molnar [this message]
2006-07-04 15:24   ` Daniel Walker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060704151504.GA10779@elte.hu \
    --to=mingo@elte.hu \
    --cc=arjan@infradead.org \
    --cc=dwalker@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox