From: Priit Laes <plaes@plaes.org>
To: kvm@vger.kernel.org
Subject: Lock warning traceback
Date: Tue, 29 Sep 2009 08:56:24 +0300 [thread overview]
Message-ID: <1254203784.2432.4.camel@chi> (raw)
Hi!
I've been getting some locking-related warning when I fire up a KVM
machine. This has been popping up since a 2.6.30 kernel:
[snip]
[119206.978058] BUG: MAX_LOCK_DEPTH too low!
[119206.978062] turning off the locking correctness validator.
[119206.978067] Pid: 9510, comm: kvm Not tainted 2.6.31 #44
[119206.978071] Call Trace:
[119206.978080] [<ffffffff8108e4a9>] __lock_acquire+0x94c/0x974
[119206.978086] [<ffffffff8108e59d>] lock_acquire+0xcc/0xe9
[119206.978092] [<ffffffff810e106f>] ? mm_take_all_locks+0xd9/0x110
[119206.978099] [<ffffffff814af652>] ? mutex_lock_nested+0x23b/0x24a
[119206.978104] [<ffffffff810e0fd0>] ? mm_take_all_locks+0x3a/0x110
[119206.978109] [<ffffffff814b05b9>] _spin_lock_nest_lock+0x2c/0x3b
[119206.978114] [<ffffffff810e106f>] ? mm_take_all_locks+0xd9/0x110
[119206.978119] [<ffffffff810e106f>] mm_take_all_locks+0xd9/0x110
[119206.978125] [<ffffffff810efe83>] do_mmu_notifier_register
+0xa8/0x16a
[119206.978130] [<ffffffff810eff60>] mmu_notifier_register+0xe/0x10
[119206.978136] [<ffffffff8100daba>] kvm_dev_ioctl+0x136/0x2ed
[119206.978142] [<ffffffff811061f9>] vfs_ioctl+0x1d/0x82
[119206.978147] [<ffffffff81106730>] do_vfs_ioctl+0x45b/0x4a1
[119206.978153] [<ffffffff811fdb78>] ? __up_read+0x9a/0xa2
[119206.978158] [<ffffffff8108287b>] ? up_read+0x26/0x2a
[119206.978163] [<ffffffff811067b8>] sys_ioctl+0x42/0x65
[119206.978169] [<ffffffff810329eb>] system_call_fastpath+0x16/0x1b
[119216.471426] kvm: emulating exchange as write
[/snip]
Although, this does not seem to be critical as my guest op-system seems
to be working fine...
Päikest,
Priit :)
next reply other threads:[~2009-09-29 6:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 5:56 Priit Laes [this message]
2009-09-29 16:50 ` Lock warning traceback Marcelo Tosatti
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=1254203784.2432.4.camel@chi \
--to=plaes@plaes.org \
--cc=kvm@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