"make check-valgrind" points to memory leak issue in case memory is allocated within one of ovsdb_idl_column.parse() functions. More details can be found in pull request https://github.com/openvswitch/ovs/pull/290.
Each issue can be solved in many different ways. This one was solved by modifying struct ovsdb_idl_row what I considered to be the optimal way. However modifying data structures can bring some potential risks currently not envisaged to me (I'm a novice in OVS code). So the main purpose of this patch is to find out what is the level of freedom for modifying existing data structures. Signed-off-by: Damijan Skvarc <damjan.skv...@gmail.com> Submitted-at: https://github.com/openvswitch/ovs/pull/290. _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
