Re: [PATCH] OpenVZ driver: fix openvzGetVPSUUID()

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

 



2011/5/27 Jean-Baptiste Rouault <jean-baptiste.rouault@xxxxxxxxxxx>:
> On Friday 27 May 2011 16:01:32 Matthias Bolte wrote:
>> Thanks, pushed then.
>>
>> There are other usages of getline in the OpenVZ driver, but they
>> should all be safe because they don't distinguish between 0 and -1,
>> except openvzGetProcessInfo.
>>
>> Jean-Baptiste could you test virsh dominfo of a running OpenVZ domain?
>> I expect it to currently fail and will post a patch for it.
>>
>> Matthias
>
> virsh dominfo on a running domain doesn't fail here :
>> virsh # dominfo 100
>> ID : Â Â Â Â Â 100
>> Nom : Â Â Â Â Â100
>> UUID : Â Â Â Â 0a0cf7cb-efb4-4065-ac2d-e63ad51e72cf
>> Type de SE : Â exe
>> Ãtat : Â Â Â Âen cours d'exÃcution
>> CPU : Â Â Â Â Â1
>> Temps CPU : Â Â2,3s
>> MÃmoire Max : 262144 kB
>> MÃmoire utilisÃe : 262144 kB
>> Persistent: Â Â yes
>> Autostart: Â Â Âdisable
>
> I tried it on a stopped domain and it doesn't fail either.
>
> Jean-Baptiste

Ah, makes sense, openvzGetProcessInfo doesn't normally run in the
situation where getline hits EOF because the loop will find the
appropriate line and exit the loop. Thanks for testing.

I'll post a patch to restore the original EOF handling even if it's
not critical.

Matthias

--
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]