Re: [PATCH] KVM: Free new dirty bitmap if creating a new memslot fails

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH] KVM: Free new dirty bitmap if creating a new memslot fails
From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
Date: Fri, 20 May 2022 09:44:27 -0400
Cc: kvm@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, syzbot+8606b8a9cc97a63f1c87@xxxxxxxxxxxxxxxxxxxxxxxxx
In-reply-to: <20220518003842.1341782-1-seanjc@google.com>
References:

Queued, thanks.

Paolo

References:
- [PATCH] KVM: Free new dirty bitmap if creating a new memslot fails
  - From: Sean Christopherson

Prev by Date: Re: [PATCH] KVM: x86: Move kzalloc out of atomic context on PREEMPT_RT
Next by Date: Re: [PATCH v3 1/1] vfio: remove VFIO_GROUP_NOTIFY_SET_KVM
Previous by thread: [PATCH] KVM: Free new dirty bitmap if creating a new memslot fails
Next by thread: [Bug 215995] New: error: array subscript 32 is above array bounds of ‘long unsigned int[17]’
Index(es):
- Date
- Thread

[Index of Archives] [KVM ARM] [KVM ia64] [KVM ppc] [Virtualization Tools] [Spice Development] [Libvirt] [Libvirt Users] [Linux USB Devel] [Linux Audio Users] [Yosemite Questions] [Linux Kernel] [Linux SCSI] [XFree86]

Powered by Linux