From: James Bottomley <James.Bottomley@SteelEye.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Arjan van de Ven <arjan@infradead.org>
Subject: Mysterious lockdep warning from the SCSI workqueue code
Date: Sat, 22 Dec 2007 11:27:32 -0600 [thread overview]
Message-ID: <1198344452.3478.9.camel@localhost.localdomain> (raw)
I've no idea why this is occurring:
WARNING: at kernel/lockdep.c:700 look_up_lock_class()
Pid: 2068, comm: scsi_wq_3 Not tainted 2.6.24-rc6 #38
[<c010535a>] show_trace_log_lvl+0x1a/0x30
[<c0105ce2>] show_trace+0x12/0x20
[<c010601c>] dump_stack+0x6c/0x80
[<c014696d>] __lock_acquire+0x46d/0x10b0
[<c0147628>] lock_acquire+0x78/0xa0
[<c0136d18>] run_workqueue+0x128/0x1d0
[<c013795c>] worker_thread+0x8c/0xf0
[<c013ab32>] kthread+0x42/0x70
[<c0104f47>] kernel_thread_helper+0x7/0x10
=======================
it looks to be happening on the initial workqueue.c:run_workqueue()
spin_lock_irq(&cwq->lock);
It's caused by lockdep.c:look_up_lock_class()
WARN_ON_ONCE(class->name != lock->name);
but I'm not entirely sure what this actually means, not fully
understanding lockdep classes and how we acquire them in scsi.
James
next reply other threads:[~2007-12-22 17:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-22 17:27 James Bottomley [this message]
2007-12-22 22:56 ` Mysterious lockdep warning from the SCSI workqueue code Rafael J. Wysocki
2007-12-22 23:16 ` Peter Zijlstra
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=1198344452.3478.9.camel@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.