From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Anatoly Burakov <anatoly.burakov@intel.com>
Subject: [PATCH v2 1/6] eal: take experimental flag off of rte_memeq_timingsafe
Date: Mon, 29 Jun 2026 11:59:24 -0700 [thread overview]
Message-ID: <20260629190027.2071745-2-stephen@networkplumber.org> (raw)
In-Reply-To: <20260629190027.2071745-1-stephen@networkplumber.org>
This function is needed in other places, and don't want to
have to propagate allow_experimental_api into those drivers.
It is stable enough and inline so no ABI exposure.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
doc/guides/rel_notes/release_26_07.rst | 4 ++++
lib/eal/include/rte_memory.h | 4 ----
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/doc/guides/rel_notes/release_26_07.rst b/doc/guides/rel_notes/release_26_07.rst
index 4ca0a9ac77..ec227fd90d 100644
--- a/doc/guides/rel_notes/release_26_07.rst
+++ b/doc/guides/rel_notes/release_26_07.rst
@@ -241,6 +241,10 @@ API Changes
- ``rte_pmd_mlx5_enable_steering``
- ``rte_pmd_mlx5_disable_steering``
+* **eal: promoted timing-safe memory comparison from experimental to stable.**
+
+ The inline function ``rte_memeq_timingsafe()`` is no longer marked experimental.
+
ABI Changes
-----------
diff --git a/lib/eal/include/rte_memory.h b/lib/eal/include/rte_memory.h
index b6e97ad695..940770f1eb 100644
--- a/lib/eal/include/rte_memory.h
+++ b/lib/eal/include/rte_memory.h
@@ -747,9 +747,6 @@ void
rte_memzero_explicit(void *dst, size_t sz);
/**
- * @warning
- * @b EXPERIMENTAL: this API may change without prior notice.
- *
* Timing-safe memory equality comparison.
*
* This function compares two memory regions in constant time,
@@ -770,7 +767,6 @@ rte_memzero_explicit(void *dst, size_t sz);
* @return
* true if the memory regions are identical, false if they differ.
*/
-__rte_experimental
static inline bool
rte_memeq_timingsafe(const void *a, const void *b, size_t n)
{
--
2.53.0
next prev parent reply other threads:[~2026-06-29 19:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 15:56 [PATCH 0/5] crypto: use timing-safe digest comparison Stephen Hemminger
2026-06-25 15:56 ` [PATCH 1/5] eal: take experimental flag off of rte_memeq_timingsafe Stephen Hemminger
2026-06-25 15:56 ` [PATCH 2/5] crypto/uadk: use timing-safe digest comparison Stephen Hemminger
2026-06-25 15:56 ` [PATCH 3/5] crypto/ccp: " Stephen Hemminger
2026-06-25 15:56 ` [PATCH 4/5] crypto/armv8: " Stephen Hemminger
2026-06-26 17:11 ` Jack Bond-Preston
2026-06-25 15:56 ` [PATCH 5/5] crypto/cnxk: " Stephen Hemminger
2026-06-29 6:42 ` [EXTERNAL] " Tejasree Kondoj
2026-06-29 7:38 ` [EXTERNAL] [PATCH 0/5] crypto: " Akhil Goyal
2026-06-29 18:59 ` [PATCH v2 0/6] " Stephen Hemminger
2026-06-29 18:59 ` Stephen Hemminger [this message]
2026-06-29 18:59 ` [PATCH v2 2/6] crypto/uadk: " Stephen Hemminger
2026-06-29 18:59 ` [PATCH v2 3/6] crypto/ccp: " Stephen Hemminger
2026-06-29 18:59 ` [PATCH v2 4/6] crypto/armv8: " Stephen Hemminger
2026-06-29 18:59 ` [PATCH v2 5/6] crypto/cnxk: " Stephen Hemminger
2026-06-29 18:59 ` [PATCH v2 6/6] crypto/octeontx: use timing-safe RSA signature verification Stephen Hemminger
2026-06-30 9:50 ` [EXTERNAL] " Tejasree Kondoj
2026-06-30 17:22 ` [PATCH v2 0/6] crypto: use timing-safe digest comparison Morten Brørup
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260629190027.2071745-2-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox