On 1/7/25 15:49, Mike Pattrick wrote: > Calls to ovs_fatal from check_ovsdb_error would trigger an asan splat in > the ci. This is a harmless memory leak as the process would always > immediately terminate anyways. > > ==245041==ERROR: LeakSanitizer: detected memory leaks > > Direct leak of 32 byte(s) in 1 object(s) allocated from: > #0 in malloc > #1 in xmalloc__ lib/util.c:141:15 > #2 in xmalloc lib/util.c:176:12 > #3 in ovsdb_error_valist lib/ovsdb-error.c:40:33 > #4 in ovsdb_error lib/ovsdb-error.c:55:13 > #5 in ovsdb_log_open ovsdb/log.c > #6 in do_db_name ovsdb/ovsdb-tool.c:482:23 > #7 in ovs_cmdl_run_command__ lib/command-line.c:247:17 > #8 in main ovsdb/ovsdb-tool.c:82:5 > > Signed-off-by: Mike Pattrick <[email protected]>
Applied this one patch and backported down to 3.3. Thanks! Best regards, Ilya Maximets. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
