From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1446] Fortify warnings in rte_pcapng
Date: Mon, 20 May 2024 23:20:08 +0000 [thread overview]
Message-ID: <bug-1446-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 3741 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1446
Bug ID: 1446
Summary: Fortify warnings in rte_pcapng
Product: DPDK
Version: 24.03
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: minor
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
On Ubuntu 22.04 build:
In file included from /usr/include/string.h:548,
from ../lib/pcapng/rte_pcapng.c:9:
In function ‘memcpy’,
inlined from ‘pcapng_add_option’ at ../lib/pcapng/rte_pcapng.c:131:2,
inlined from ‘pcapng_section_block’ at ../lib/pcapng/rte_pcapng.c:192:8:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:29:10: warning: argument
2 null where non-null expected [-Wnonnull]
29 | return __builtin___memcpy_chk (__dest, __src, __len,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
30 | __glibc_objsize0 (__dest));
| ~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:29:10: note: in a call to
built-in function ‘__builtin___memcpy_chk’
In function ‘memcpy’,
inlined from ‘pcapng_add_option’ at ../lib/pcapng/rte_pcapng.c:131:2,
inlined from ‘rte_pcapng_add_interface’ at
../lib/pcapng/rte_pcapng.c:308:8:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:29:10: warning: argument
2 null where non-null expected [-Wnonnull]
29 | return __builtin___memcpy_chk (__dest, __src, __len,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
30 | __glibc_objsize0 (__dest));
| ~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:29:10: note: in a call to
built-in function ‘__builtin___memcpy_chk’
In function ‘memcpy’,
inlined from ‘pcapng_add_option’ at ../lib/pcapng/rte_pcapng.c:131:2,
inlined from ‘rte_pcapng_write_stats’ at ../lib/pcapng/rte_pcapng.c:371:9:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:29:10: warning: argument
2 null where non-null expected [-Wnonnull]
29 | return __builtin___memcpy_chk (__dest, __src, __len,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
30 | __glibc_objsize0 (__dest));
| ~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:29:10: note: in a call to
built-in function ‘__builtin___memcpy_chk’
[1964/2680] Compiling C object
drivers/libtmp_rte_net_virtio.a.p/net_virtio_virtio_user_vhost_user.c.o
In file included from /usr/include/string.h:548,
from /usr/include/x86_64-linux-gnu/sys/un.h:38,
from ../drivers/net/virtio/virtio_user/vhost_user.c:10:
In function ‘memcpy’,
inlined from ‘vhost_user_write.constprop’ at
../drivers/net/virtio/virtio_user/vhost_user.c:131:2:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:29:10: warning: argument
2 null where non-null expected [-Wnonnull]
29 | return __builtin___memcpy_chk (__dest, __src, __len,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
30 | __glibc_objsize0 (__dest));
| ~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:29:10: note: in a call to
built-in function ‘__builtin___memcpy_chk’
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 5599 bytes --]
reply other threads:[~2024-05-20 23:20 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-1446-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).