KVM: fix crash on irqfd deassign
irqfd in kvm used flush_work incorrectly: it assumed that work scheduled previously can't run after flush_work, but since kvm uses a non-reentrant workqueue (by means of schedule_work) we need flush_work_sync to get that guarantee. Signed-off-by: Michael S. Tsirkin <mst@redhat.com> Reported-by: Jean-Philippe Menil <jean-philippe.menil@univ-nantes.fr> Tested-by: Jean-Philippe Menil <jean-philippe.menil@univ-nantes.fr> Signed-off-by: Avi Kivity <avi@redhat.com>
This commit is contained in:
Родитель
6221f222c0
Коммит
9e02fb9633
|
@ -90,7 +90,7 @@ irqfd_shutdown(struct work_struct *work)
|
||||||
* We know no new events will be scheduled at this point, so block
|
* We know no new events will be scheduled at this point, so block
|
||||||
* until all previously outstanding events have completed
|
* until all previously outstanding events have completed
|
||||||
*/
|
*/
|
||||||
flush_work(&irqfd->inject);
|
flush_work_sync(&irqfd->inject);
|
||||||
|
|
||||||
/*
|
/*
|
||||||
* It is now safe to release the object's resources
|
* It is now safe to release the object's resources
|
||||||
|
|
Загрузка…
Ссылка в новой задаче