On 08/09/2016 07:13 PM, Christoffer Dall wrote: > KVM devices were manipulating list data structures without any form of > synchronization, and some implementations of the create operations also > suffered from a lack of synchronization. > > Now when we've split the xics create operation into create and init, we > can hold the kvm->lock mutex while calling the create operation and when > manipulating the devices list. > > The error path in the generic code gets slightly ugly because we have to > take the mutex again and delete the device from the list, but holding > the mutex during anon_inode_getfd or releasing/locking the mutex in the > common non-error path seemed wrong. > > Signed-off-by: Christoffer Dall <christoffer.dall@xxxxxxxxxx> > Reviewed-by: Paolo Bonzini <pbonzini@xxxxxxxxxx> Looks sane for s390. Acked-by: Christian Borntraeger <borntraeger@xxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
