On 2/3/22 17:33, Paolo Valerio wrote: > Dumitru Ceara <dce...@redhat.com> writes: > >> It's actually undefined behavior to pass NULL to standard library >> functions that manipulate arrays (e.g., qsort, memcpy, memcmp), even if >> the passed number of items is 0. >> >> UB Sanitizer reports: >> ovsdb/monitor.c:408:9: runtime error: null pointer passed as argument 1, >> which is declared to never be null >> #0 0x406ae1 in ovsdb_monitor_columns_sort ovsdb/monitor.c:408 >> #1 0x406ae1 in ovsdb_monitor_add ovsdb/monitor.c:1683 >> [...] >> lib/ovsdb-data.c:1970:5: runtime error: null pointer passed as argument 2, >> which is declared to never be null >> #0 0x4071c8 in ovsdb_datum_push_unsafe lib/ovsdb-data.c:1970 >> #1 0x471cd0 in ovsdb_datum_apply_diff_in_place lib/ovsdb-data.c:2345 >> [...] >> ofproto/ofproto-dpif-rid.c:159:17: runtime error: null pointer passed as >> argument 1, which is declared to never be null >> #0 0x4df5d8 in frozen_state_equal ofproto/ofproto-dpif-rid.c:159 >> #1 0x4dfd27 in recirc_find_equal ofproto/ofproto-dpif-rid.c:179 >> [...] >> >> Acked-by: Aaron Conole <acon...@redhat.com> >> Signed-off-by: Dumitru Ceara <dce...@redhat.com> >> --- > > Acked-by: Paolo Valerio <pvale...@redhat.com> >
Thanks! Applied to master and 2.17. Best regards, Ilya Maximets. _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
