From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1862] mlx5: errors when built with LTO
Date: Wed, 31 Dec 2025 17:58:21 +0000 [thread overview]
Message-ID: <bug-1862-3@http.bugs.dpdk.org/> (raw)
http://bugs.dpdk.org/show_bug.cgi?id=1862
Bug ID: 1862
Summary: mlx5: errors when built with LTO
Product: DPDK
Version: 25.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
Building with LTO and release flags causes lots of warnings in mlx5
[3686/3710] Linking target drivers/librte_net_mlx5.so.26.1
In function ‘mlx5dr_action_prepare_decap_l3_data’,
inlined from ‘mlx5dr_action_handle_tunnel_l3_to_l2’ at
../drivers/net/mlx5/hws/mlx5dr_action.c:2164:3,
inlined from ‘mlx5dr_action_create_reformat_hws’ at
../drivers/net/mlx5/hws/mlx5dr_action.c:2234:9:
../drivers/net/mlx5/hws/mlx5dr_action.c:3643:17: warning: writing 4 bytes into
a region of size 0 [-Wstringop-overflow=]
3643 | memcpy(dst, e_src, MLX5DR_ACTION_INLINE_DATA_SIZE); /*
data */
| ^
../drivers/net/mlx5/hws/mlx5dr_action.c: In function
‘mlx5dr_action_create_reformat_hws’:
../drivers/net/mlx5/hws/mlx5dr_action.c:2144:17: note: at offset [140, 524248]
into destination object ‘mh_data’ of size 64
2144 | uint8_t mh_data[MLX5DR_ACTION_REFORMAT_DATA_SIZE] = {0};
| ^
../drivers/net/mlx5/hws/mlx5dr_action.c:2144:17: note: at offset [12, 64] into
destination object ‘mh_data’ of size 64
../drivers/net/mlx5/hws/mlx5dr_action.c:2144:17: note: at offset [140, 524248]
into destination object ‘mh_data’ of size 64
In function ‘mlx5dr_action_prepare_decap_l3_data’,
inlined from ‘mlx5dr_action_handle_tunnel_l3_to_l2’ at
../drivers/net/mlx5/hws/mlx5dr_action.c:2164:3,
inlined from ‘mlx5dr_action_create_reformat_hws’ at
../drivers/net/mlx5/hws/mlx5dr_action.c:2234:9:
../drivers/net/mlx5/hws/mlx5dr_action.c:3643:17: warning: writing 4 bytes into
a region of size 0 [-Wstringop-overflow=]
3643 | memcpy(dst, e_src, MLX5DR_ACTION_INLINE_DATA_SIZE); /*
data */
| ^
../drivers/net/mlx5/hws/mlx5dr_action.c: In function
‘mlx5dr_action_create_reformat_hws’:
../drivers/net/mlx5/hws/mlx5dr_action.c:2144:17: note: at offset [148, 524256]
into destination object ‘mh_data’ of size 64
2144 | uint8_t mh_data[MLX5DR_ACTION_REFORMAT_DATA_SIZE] = {0};
| ^
../drivers/net/mlx5/hws/mlx5dr_action.c:2144:17: note: at offset [20, 64] into
destination object ‘mh_data’ of size 64
../drivers/net/mlx5/hws/mlx5dr_action.c:2144:17: note: at offset [148, 524256]
into destination object ‘mh_data’ of size 64
In function ‘mlx5dr_action_prepare_decap_l3_data’,
inlined from ‘mlx5dr_action_handle_tunnel_l3_to_l2’ at
../drivers/net/mlx5/hws/mlx5dr_action.c:2164:3,
inlined from ‘mlx5dr_action_create_reformat_hws’ at
../drivers/net/mlx5/hws/mlx5dr_action.c:2234:9:
../drivers/net/mlx5/hws/mlx5dr_action.c:3643:17: warning: writing 4 bytes into
a region of size 0 [-Wstringop-overflow=]
3643 | memcpy(dst, e_src, MLX5DR_ACTION_INLINE_DATA_SIZE); /*
data */
| ^
../drivers/net/mlx5/hws/mlx5dr_action.c: In function
‘mlx5dr_action_create_reformat_hws’:
../drivers/net/mlx5/hws/mlx5dr_action.c:2144:17: note: at offset [156, 524264]
into destination object ‘mh_data’ of size 64
2144 | uint8_t mh_data[MLX5DR_ACTION_REFORMAT_DATA_SIZE] = {0};
| ^
../drivers/net/mlx5/hws/mlx5dr_action.c:2144:17: note: at offset [28, 64] into
destination object ‘mh_data’ of size 64
../drivers/net/mlx5/hws/mlx5dr_action.c:2144:17: note: at offset [156, 524264]
into destination object ‘mh_data’ of size 64
In function ‘mlx5dr_action_prepare_decap_l3_data’,
inlined from ‘mlx5dr_action_handle_tunnel_l3_to_l2’ at
../drivers/net/mlx5/hws/mlx5dr_action.c:2164:3,
inlined from ‘mlx5dr_action_create_reformat_hws’ at
../drivers/net/mlx5/hws/mlx5dr_action.c:2234:9:
../drivers/net/mlx5/hws/mlx5dr_action.c:3643:17: warning: writing 4 bytes into
a region of size 0 [-Wstringop-overflow=]
3643 | memcpy(dst, e_src, MLX5DR_ACTION_INLINE_DATA_SIZE); /*
data */
| ^
../drivers/net/mlx5/hws/mlx5dr_action.c: In function
‘mlx5dr_action_create_reformat_hws’:
../drivers/net/mlx5/hws/mlx5dr_action.c:2144:17: note: at offset [164, 524272]
into destination object ‘mh_data’ of size 64
2144 | uint8_t mh_data[MLX5DR_ACTION_REFORMAT_DATA_SIZE] = {0};
| ^
../drivers/net/mlx5/hws/mlx5dr_action.c:2144:17: note: at offset [36, 64] into
destination object ‘mh_data’ of size 64
../drivers/net/mlx5/hws/mlx5dr_action.c:2144:17: note: at offset [164, 524272]
into destination object ‘mh_data’ of size 64
In function ‘mlx5dr_action_prepare_decap_l3_data’,
inlined from ‘mlx5dr_action_handle_tunnel_l3_to_l2’ at
../drivers/net/mlx5/hws/mlx5dr_action.c:2164:3,
inlined from ‘mlx5dr_action_create_reformat_hws’ at
../drivers/net/mlx5/hws/mlx5dr_action.c:2234:9:
../drivers/net/mlx5/hws/mlx5dr_action.c:3643:17: warning: writing 4 bytes into
a region of size 0 [-Wstringop-overflow=]
3643 | memcpy(dst, e_src, MLX5DR_ACTION_INLINE_DATA_SIZE); /*
data */
| ^
../drivers/net/mlx5/hws/mlx5dr_action.c: In function
‘mlx5dr_action_create_reformat_hws’:
../drivers/net/mlx5/hws/mlx5dr_action.c:2144:17: note: at offset [172, 524280]
into destination object ‘mh_data’ of size 64
2144 | uint8_t mh_data[MLX5DR_ACTION_REFORMAT_DATA_SIZE] = {0};
| ^
../drivers/net/mlx5/hws/mlx5dr_action.c:2144:17: note: at offset [44, 64] into
destination object ‘mh_data’ of size 64
../drivers/net/mlx5/hws/mlx5dr_action.c:2144:17: note: at offset [172, 524280]
into destination object ‘mh_data’ of size 64
In function ‘mlx5dr_action_prepare_decap_l3_data’,
inlined from ‘mlx5dr_action_handle_tunnel_l3_to_l2’ at
../drivers/net/mlx5/hws/mlx5dr_action.c:2164:3,
inlined from ‘mlx5dr_action_create_reformat_hws’ at
../drivers/net/mlx5/hws/mlx5dr_action.c:2234:9:
../drivers/net/mlx5/hws/mlx5dr_action.c:3643:17: warning: writing 4 bytes into
a region of size 0 [-Wstringop-overflow=]
3643 | memcpy(dst, e_src, MLX5DR_ACTION_INLINE_DATA_SIZE); /*
data */
| ^
../drivers/net/mlx5/hws/mlx5dr_action.c: In function
‘mlx5dr_action_create_reformat_hws’:
../drivers/net/mlx5/hws/mlx5dr_action.c:2144:17: note: at offset [180, 524288]
into destination object ‘mh_data’ of size 64
2144 | uint8_t mh_data[MLX5DR_ACTION_REFORMAT_DATA_SIZE] = {0};
| ^
../drivers/net/mlx5/hws/mlx5dr_action.c:2144:17: note: at offset [52, 64] into
destination object ‘mh_data’ of size 64
../drivers/net/mlx5/hws/mlx5dr_action.c:2144:17: note: at offset [180, 524288]
into destination object ‘mh_data’ of size 64
In function ‘mlx5dr_action_prepare_decap_l3_data’,
inlined from ‘mlx5dr_action_handle_tunnel_l3_to_l2’ at
../drivers/net/mlx5/hws/mlx5dr_action.c:2164:3,
inlined from ‘mlx5dr_action_create_reformat_hws’ at
../drivers/net/mlx5/hws/mlx5dr_action.c:2234:9:
../drivers/net/mlx5/hws/mlx5dr_action.c:3643:17: warning: writing 4 bytes into
a region of size 0 [-Wstringop-overflow=]
3643 | memcpy(dst, e_src, MLX5DR_ACTION_INLINE_DATA_SIZE); /*
data */
| ^
../drivers/net/mlx5/hws/mlx5dr_action.c: In function
‘mlx5dr_action_create_reformat_hws’:
../drivers/net/mlx5/hws/mlx5dr_action.c:2144:17: note: at offset [188, 524296]
into destination object ‘mh_data’ of size 64
2144 | uint8_t mh_data[MLX5DR_ACTION_REFORMAT_DATA_SIZE] = {0};
| ^
../drivers/net/mlx5/hws/mlx5dr_action.c:2144:17: note: at offset [60, 64] into
destination object ‘mh_data’ of size 64
../drivers/net/mlx5/hws/mlx5dr_action.c:2144:17: note: at offset [188, 524296]
into destination object ‘mh_data’ of size 64
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2025-12-31 17:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-1862-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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;
as well as URLs for NNTP newsgroup(s).