
11 Jun
2018
11 Jun
'18
6:21 a.m.
On Fri, Jun 08, 2018 at 17:11:55 -0300, Julio Faracco wrote:
Since virConfGetValueBool() can return earlier, the parameter 'value' might be not initialised properly inside this method. Another proof:
Yeah, the problem is that if the value is not found, virConfGetValueBool returns 0 which I did not notice. I think a better fix will be to execute the condition checking 'tmp' only when virConfGetValueBool returns 1 as we care only if the user set the unsupported configuration.