Konstantin Ananyev, Feb 06, 2023 at 21:44: > > Ok I see. But what should we do to prevent this? Simply ignore the > > request and log a warning? > > That's seems like simplest choice to me... Or if you still prefer to > allow it - put a special comment that it is user responsibility to > handle such possible race-condition (inside his CB function or so).
The issue is that a warning can be easily overlooked and the application may assume that they can free up resources whereas the callback was never reset and may still access them. I wonder if this could be enforced with RTE_BUILD_BUG_ON somehow. Or at least by checking that the cb value is not NULL with RTE_ASSERT?
