From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1511] net/tap build failure on Ubuntu 24.04 with LTO
Date: Sun, 04 Aug 2024 20:56:51 +0000 [thread overview]
Message-ID: <bug-1511-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 3834 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1511
Bug ID: 1511
Summary: net/tap build failure on Ubuntu 24.04 with LTO
Product: DPDK
Version: 24.07
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: alialnu@nvidia.com
Target Milestone: ---
$ meson --werror -Db_lto=true build && ninja -C build
[..]
[2109/2774] Linking target drivers/librte_net_tap.so.24.2
../drivers/net/tap/tap_netlink.c: In function ‘tap_flow_create_ipv6’:
../drivers/net/tap/tap_netlink.c:305:9: warning: writing 16 bytes into a region
of size 12 [-Wstringop-overflow=]
305 | memcpy(RTA_DATA(rta), data, data_len);
| ^
../drivers/net/tap/tap_netlink.h:20:25: note: at offset [4, 16] into
destination object ‘nh’ of size 16
20 | struct nlmsghdr nh;
| ^
../drivers/net/tap/tap_netlink.c:305:9: warning: writing 16 bytes into a region
of size 12 [-Wstringop-overflow=]
305 | memcpy(RTA_DATA(rta), data, data_len);
| ^
../drivers/net/tap/tap_netlink.h:20:25: note: at offset [4, 16] into
destination object ‘nh’ of size 16
20 | struct nlmsghdr nh;
| ^
../drivers/net/tap/tap_netlink.c:305:9: warning: writing 16 bytes into a region
of size 12 [-Wstringop-overflow=]
305 | memcpy(RTA_DATA(rta), data, data_len);
| ^
../drivers/net/tap/tap_netlink.h:20:25: note: at offset [4, 16] into
destination object ‘nh’ of size 16
20 | struct nlmsghdr nh;
| ^
../drivers/net/tap/tap_netlink.c:305:9: warning: writing 16 bytes into a region
of size 12 [-Wstringop-overflow=]
305 | memcpy(RTA_DATA(rta), data, data_len);
| ^
../drivers/net/tap/tap_netlink.h:20:25: note: at offset [4, 16] into
destination object ‘nh’ of size 16
20 | struct nlmsghdr nh;
| ^
[2755/2774] Linking target app/dpdk-test-pipeline
../drivers/net/tap/tap_netlink.c: In function ‘tap_flow_create_ipv6’:
../drivers/net/tap/tap_netlink.c:305:9: warning: writing 16 bytes into a region
of size 12 [-Wstringop-overflow=]
305 | memcpy(RTA_DATA(rta), data, data_len);
| ^
../drivers/net/tap/tap_netlink.h:20:25: note: at offset [4, 16] into
destination object ‘nh’ of size 16
20 | struct nlmsghdr nh;
| ^
../drivers/net/tap/tap_netlink.c:305:9: warning: writing 16 bytes into a region
of size 12 [-Wstringop-overflow=]
305 | memcpy(RTA_DATA(rta), data, data_len);
| ^
../drivers/net/tap/tap_netlink.h:20:25: note: at offset [4, 16] into
destination object ‘nh’ of size 16
20 | struct nlmsghdr nh;
| ^
../drivers/net/tap/tap_netlink.c:305:9: warning: writing 16 bytes into a region
of size 12 [-Wstringop-overflow=]
305 | memcpy(RTA_DATA(rta), data, data_len);
| ^
../drivers/net/tap/tap_netlink.h:20:25: note: at offset [4, 16] into
destination object ‘nh’ of size 16
20 | struct nlmsghdr nh;
| ^
../drivers/net/tap/tap_netlink.c:305:9: warning: writing 16 bytes into a region
of size 12 [-Wstringop-overflow=]
305 | memcpy(RTA_DATA(rta), data, data_len);
| ^
../drivers/net/tap/tap_netlink.h:20:25: note: at offset [4, 16] into
destination object ‘nh’ of size 16
[..]
OS: Ubuntu 24.04
Meson: 1.3.2
Compiler: gcc 13.2.0
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 5716 bytes --]
reply other threads:[~2024-08-04 20:56 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-1511-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).