On Wed, 28 Jan 2026 07:37:13 -0800 Scott Mitchell <[email protected]> wrote:
> Thanks for the context! That makes sense. I dropped rte_memcpy and can > re-evaluate once all my upcoming changes are merged. The other thing worth noting is that compilers and tools like fortify know what memcpy is and do bounds checking. But even with all the annotation to x86 rte_memcpy() it still doesn't engage all the checks. Plus there is the case (found in examples/fips_validation) where rte_memcpy would read past end of array on stack. Many platforms have rte_memcpy is just alias for memcpy. The only ones with special code are x86 and ARM64.
