diff options
author | Avi Kivity <avi@redhat.com> | 2009-01-05 15:21:42 +0200 |
---|---|---|
committer | Avi Kivity <avi@redhat.com> | 2009-03-24 11:03:01 +0200 |
commit | 269e05e48502f1cc06802e9fba90f5100dd6bb0d (patch) | |
tree | 9b3501dc1f5e137c2dca7eacf15c0353f627be97 /arch/x86/kvm/i8254.c | |
parent | a77ab5ead5c1fef2c6c5a9b3cf3765e52643a2aa (diff) | |
download | linux-269e05e48502f1cc06802e9fba90f5100dd6bb0d.tar.bz2 |
KVM: Properly lock PIT creation
Otherwise, two threads can create a PIT in parallel and cause a memory leak.
Signed-off-by: Avi Kivity <avi@redhat.com>
Diffstat (limited to 'arch/x86/kvm/i8254.c')
-rw-r--r-- | arch/x86/kvm/i8254.c | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/arch/x86/kvm/i8254.c b/arch/x86/kvm/i8254.c index 528daadeba49..69d1bbff3fd3 100644 --- a/arch/x86/kvm/i8254.c +++ b/arch/x86/kvm/i8254.c @@ -548,9 +548,7 @@ struct kvm_pit *kvm_create_pit(struct kvm *kvm) if (!pit) return NULL; - mutex_lock(&kvm->lock); pit->irq_source_id = kvm_request_irq_source_id(kvm); - mutex_unlock(&kvm->lock); if (pit->irq_source_id < 0) { kfree(pit); return NULL; |