11/06/2025 16:57, Stephen Hemminger:
> On Wed, 11 Jun 2025 14:34:49 +0200
> Thomas Monjalon wrote:
>
> > 20/02/2025 17:27, Stephen Hemminger:
> > > --- a/lib/eal/include/rte_string_fns.h
> > > +++ b/lib/eal/include/rte_string_fns.h
> > > +__rte_experimental
> > > +void
> > > +rte_memzero_explicit
20/02/2025 17:27, Stephen Hemminger:
> --- a/lib/eal/include/rte_string_fns.h
> +++ b/lib/eal/include/rte_string_fns.h
> +__rte_experimental
> +void
> +rte_memzero_explicit(void *dst, size_t sz);
This function is not about strings.
Better to move it to rte_memory.h (even if not ideal).
I'll try to
When memset() is used before a release function such as free,
the compiler if allowed to optimize the memset away under
the as-if rules. This is normally ok, but in certain cases such
as passwords or security keys it is problematic.
Introduce a DPDK wrapper which uses the bzero_explicit function
o
3 matches
Mail list logo