Re: [PATCH] virnet*: Don't unlock object in dispose

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

 



On Tue, Mar 10, 2015 at 11:20:14AM +0100, Michal Privoznik wrote:
> As of bba93d40 all of our RPC objects are derived from
> virObjectLockable. However, during rewrite some errors sneaked
> in. For instance, the dispose functions to virNetClient and
> virNetServerClient objects were not only freeing allocated
> memory, but unlocking themselves. This is wrong. Object should
> never disappear while locked.

ACK, ref counting ensures we have the only reference and are
unlocked when dispose runs.


Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list




[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]