03/06/2022 16:36, Kevin Laatz: > During EAL init, all buses are probed and the devices found are > initialized. On eal_cleanup(), the inverse does not happen, meaning any > allocated memory and other configuration will not be cleaned up > appropriately on exit. [...] > --- a/devtools/libabigail.abignore > +++ b/devtools/libabigail.abignore > @@ -56,3 +56,12 @@ > ; Ignore libabigail false-positive in clang builds, after moving code. > [suppress_function] > name = rte_eal_remote_launch > + > +; Ignore field inserted to rte_bus, adding cleanup function > +[suppress_type] > + name = rte_bus > + has_data_member_inserted_at = end > + > +; Ignore changes to internally used structs containing rte_bus > +[suppress_type] > + name = rte_pci_bus, rte_vmbus_bus, rte_vdev_bus
I'm not sure we can safely consider these structs as internal. The right process is to send a deprecation notice, and then remove them from the public API. For info, Li has sent a patch for the bus cleanup which is not updating the bus code: https://patches.dpdk.org/project/dpdk/patch/20220606114650.209612-3-l...@nvidia.com/ It may be a temporary solution before the deprecation.
