v1 -> v2: range_end_atom is allocated in ovsdb_atom_from_string__() and no one is holding a reference to it at the end of do_parse_atom_strings(). It should be freed, as also pointed out by ovsdb_atom_destroy().
Valgrind report is as below: 16 bytes in 1 blocks are definitely lost in loss record 2 of 5 at 0x4C2DB8F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) by 0x43F5F4: xmalloc (util.c:120) by 0x424AC6: alloc_default_atoms (ovsdb-data.c:315) by 0x4271E0: ovsdb_atom_from_string__ (ovsdb-data.c:508) by 0x4271E0: ovsdb_atom_from_string (ovsdb-data.c:632) by 0x40ADCC: do_parse_atom_strings (test-ovsdb.c:566) by 0x41BA73: ovs_cmdl_run_command__ (command-line.c:115) by 0x4051C9: main (test-ovsdb.c:72) _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev