[PATCH 03/20] eal: promote explicit zero and sensitive free to stable

[Stephen Hemminger <stephen@networkplumber.org>]

rte_memzero_explicit() and rte_free_sensitive() were added in 25.07 and
have not changed since. They are used by the QAT crypto driver for
asymmetric and symmetric session keys and by the ixgbe IPsec code, which
are exactly the sensitive data paths they exist for.

An API for clearing keys is of little use to applications while it is
marked as subject to change, so promote it.

Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
 lib/eal/common/eal_common_memory.c | 2 +-
 lib/eal/common/rte_malloc.c        | 2 +-
 lib/eal/include/rte_malloc.h       | 4 ----
 lib/eal/include/rte_memory.h       | 4 ----
 4 files changed, 2 insertions(+), 10 deletions(-)

diff --git a/lib/eal/common/eal_common_memory.c b/lib/eal/common/eal_common_memory.c
index 33681e7a37..c12b9e1e7f 100644
--- a/lib/eal/common/eal_common_memory.c
+++ b/lib/eal/common/eal_common_memory.c
@@ -1730,7 +1730,7 @@ RTE_INIT(memory_telemetry)
 
 #endif /* telemetry !RTE_EXEC_ENV_WINDOWS */
 
-RTE_EXPORT_EXPERIMENTAL_SYMBOL(rte_memzero_explicit, 25.07)
+RTE_EXPORT_SYMBOL(rte_memzero_explicit)
 void
 rte_memzero_explicit(void *dst, size_t sz)
 {
diff --git a/lib/eal/common/rte_malloc.c b/lib/eal/common/rte_malloc.c
index 388e5a63b6..0c71f26df3 100644
--- a/lib/eal/common/rte_malloc.c
+++ b/lib/eal/common/rte_malloc.c
@@ -56,7 +56,7 @@ rte_free(void *addr)
 	mem_free(addr, true, false);
 }
 
-RTE_EXPORT_EXPERIMENTAL_SYMBOL(rte_free_sensitive, 25.07)
+RTE_EXPORT_SYMBOL(rte_free_sensitive)
 void
 rte_free_sensitive(void *addr)
 {
diff --git a/lib/eal/include/rte_malloc.h b/lib/eal/include/rte_malloc.h
index 0a397e7723..c42006b594 100644
--- a/lib/eal/include/rte_malloc.h
+++ b/lib/eal/include/rte_malloc.h
@@ -53,9 +53,6 @@ rte_free(void *ptr);
 
 
 /**
- * @warning
- * @b EXPERIMENTAL: this API may change without prior notice.
- *
  * Frees the memory space pointed to by the provided pointer
  * and guarantees it will be zero'd before reuse.
  * This function is slower than simple rte_free() it should only
@@ -70,7 +67,6 @@ rte_free(void *ptr);
  * @param ptr
  *   The pointer to memory to be freed.
  */
-__rte_experimental
 void
 rte_free_sensitive(void *ptr);
 
diff --git a/lib/eal/include/rte_memory.h b/lib/eal/include/rte_memory.h
index 940770f1eb..a7749ceed1 100644
--- a/lib/eal/include/rte_memory.h
+++ b/lib/eal/include/rte_memory.h
@@ -729,9 +729,6 @@ int
 rte_mem_alloc_validator_unregister(const char *name, int socket_id);
 
 /**
- * @warning
- * @b EXPERIMENTAL: this API may change without prior notice.
- *
  * Fill memory with zero's (e.g. sensitive keys).
  * Normally using memset() is fine, but in cases where clearing out local data
  * before going out of scope is required, use rte_memzero_explicit() instead
@@ -742,7 +739,6 @@ rte_mem_alloc_validator_unregister(const char *name, int socket_id);
  * @param sz
  *   Number of bytes to fill.
  */
-__rte_experimental
 void
 rte_memzero_explicit(void *dst, size_t sz);
 
-- 
2.53.0