[v3,04/42] latency: use rte strerror

Message ID 20231114123552.398072-5-huangdengdui@huawei.com (mailing list archive)
State Changes Requested, archived
Delegated to: David Marchand
Headers
Series replace strerror |

Checks

Context Check Description
ci/checkpatch success coding style OK

Commit Message

Dengdui Huang Nov. 14, 2023, 12:35 p.m. UTC
  The function strerror() is insecure in a multi-thread environment.
This patch uses rte_strerror() to replace it.

Cc: stable@dpdk.org

Signed-off-by: Dengdui Huang <huangdengdui@huawei.com>
Acked-by: Chengwen Feng <fengchengwen@huawei.com>
---
 lib/latencystats/rte_latencystats.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
  

Patch

diff --git a/lib/latencystats/rte_latencystats.c b/lib/latencystats/rte_latencystats.c
index 8985a377db..a395f9b3bc 100644
--- a/lib/latencystats/rte_latencystats.c
+++ b/lib/latencystats/rte_latencystats.c
@@ -265,7 +265,7 @@  rte_latencystats_init(uint64_t app_samp_intvl,
 		if (ret != 0) {
 			RTE_LOG(INFO, LATENCY_STATS,
 				"Error during getting device (port %u) info: %s\n",
-				pid, strerror(-ret));
+				pid, rte_strerror(-ret));
 
 			continue;
 		}
@@ -309,7 +309,7 @@  rte_latencystats_uninit(void)
 		if (ret != 0) {
 			RTE_LOG(INFO, LATENCY_STATS,
 				"Error during getting device (port %u) info: %s\n",
-				pid, strerror(-ret));
+				pid, rte_strerror(-ret));
 
 			continue;
 		}