Signed-off-by: Chengwen Feng <fengcheng...@huawei.com> On 2025/2/12 1:35, Stephen Hemminger wrote: > 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 is equivalent to the C++ memset_s > function. Naming chosen to be similar to kernel. > > Signed-off-by: Stephen Hemminger <step...@networkplumber.org>
- [PATCH v5 00/11] memset security fixes Stephen Hemminger
- [PATCH v5 01/11] eal: introduce new secure memory f... Stephen Hemminger
- Re: [PATCH v5 01/11] eal: introduce new secure ... fengchengwen
- RE: [PATCH v5 01/11] eal: introduce new secure ... Morten Brørup
- Re: [PATCH v5 01/11] eal: introduce new sec... Stephen Hemminger
- [PATCH v5 03/11] crypto/qat: force zero of keys Stephen Hemminger
- [PATCH v5 04/11] crypto/qat: fix size calculation f... Stephen Hemminger
- [PATCH v5 05/11] crypto/qat: use secure memset Stephen Hemminger
- [PATCH v5 02/11] eal: add new secure free function Stephen Hemminger
- Re: [PATCH v5 02/11] eal: add new secure free f... fengchengwen
- Re: [PATCH v5 02/11] eal: add new secure fr... Stephen Hemminger
- [PATCH v5 06/11] bus/uacce: remove memset before fr... Stephen Hemminger
- [PATCH v5 07/11] compress/octeontx: remove unnecess... Stephen Hemminger