Re: [PATCH 00/12] OOM reporting cleanups

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

 



On Wed, Jul 02, 2014 at 12:10:53 +0200, Jano Tomko wrote:
> Patches 1-3 don't touch any code
> 4-5 no functional change
> 6 introduces a new function
> 7-8 have no functional change unless virBuffer API is misused
>   (that case resulted in an OOM error before, now it's an internal
>    error)
> 9-10 add OOM error reporting to a few functions
> 11-12 remove double OOM error reporting
> 
> Ján Tomko (12):
>   Fix indentation in bridge driver
>   More indentation fixes
>   usb: Remove redundant comment
>   Remove useless condition in networkRadvdConfContents
>   Use virStringReplace instead of openvz_replace
>   Introduce virBufferCheckError
>   Report errors in virCapabilitiesFormatXML
>   Use virBufferCheckError everywhere we report OOM error
>   Set errno on OOM in lxcProcReadMeminfo
>   Add OOM error reporting to a few fucntions
>   Remove double OOM error reporting from JSON monitor
>   Remove double OOM error reporting

ACK series after fixing the small issue I pointed out in 7/12.

Jirka

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