From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 55201] host panic when "creating guest, doing scp and killing QEMU process" continuously
Date: Sun, 7 Apr 2013 02:19:14 +0000 (UTC) [thread overview]
Message-ID: <20130407021914.0FAA011F981@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-55201-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=55201
Jay Ren <yongjie.ren@intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |CODE_FIX
--- Comment #8 from Jay Ren <yongjie.ren@intel.com> 2013-04-07 02:19:13 ---
I verified this against the latest kvm.git tree (next branch).
The following commit fixed this bug.
commit c09664bb44184b3846e8c5254db4eae4b932682a
Author: Marcelo Tosatti <mtosatti@redhat.com>
Date: Mon Mar 18 13:54:32 2013 -0300
KVM: x86: fix deadlock in clock-in-progress request handling
There is a deadlock in pvclock handling:
cpu0: cpu1:
kvm_gen_update_masterclock()
kvm_guest_time_update()
spin_lock(pvclock_gtod_sync_lock)
local_irq_save(flags)
spin_lock(pvclock_gtod_sync_lock)
kvm_make_mclock_inprogress_request(kvm)
make_all_cpus_request()
smp_call_function_many()
Now if smp_call_function_many() called by cpu0 tries to call function on
cpu1 there will be a deadlock.
Fix by moving pvclock_gtod_sync_lock protected section outside irq
disabled section.
Analyzed by Gleb Natapov <gleb@redhat.com>
Acked-by: Gleb Natapov <gleb@redhat.com>
Reported-and-Tested-by: Yongjie Ren <yongjie.ren@intel.com>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2013-04-07 2:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 2:54 [Bug 55201] New: host panic when "creating guest, doing scp and killing QEMU process" continuously bugzilla-daemon
2013-03-14 2:57 ` [Bug 55201] " bugzilla-daemon
2013-03-14 2:58 ` bugzilla-daemon
2013-03-14 10:37 ` bugzilla-daemon
2013-03-15 2:26 ` bugzilla-daemon
2013-03-15 2:27 ` bugzilla-daemon
2013-03-15 2:45 ` bugzilla-daemon
2013-03-18 13:02 ` bugzilla-daemon
2013-04-07 2:19 ` bugzilla-daemon [this message]
2013-04-07 2:19 ` bugzilla-daemon
2013-04-22 14:14 ` bugzilla-daemon
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=20130407021914.0FAA011F981@bugzilla.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.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 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.