Re: [libvirt] [PATCH 1/2] test_driver: Don't access @vm after it was set to NULL

2019-07-02 Thread Andrea Bolognani
On Tue, 2019-05-14 at 17:12 +0200, Michal Privoznik wrote: > If something goes wrong in testDomainGetDiskErrors() then we try > to free any strings that were previously allocated in return > array. Problem is, in my review of original patch (89320788ac4) > I've mistakenly did some changes which

[libvirt] [PATCH 1/2] test_driver: Don't access @vm after it was set to NULL

2019-05-14 Thread Michal Privoznik
If something goes wrong in testDomainGetDiskErrors() then we try to free any strings that were previously allocated in return array. Problem is, in my review of original patch (89320788ac4) I've mistakenly did some changes which result in possible NULL dereference (@vm is set to NULL as the first