Skip to contentSkip to conversation

Fortify warnings in rte_pcapng

DPDK/ethdev Bug 1446 [email protected] 1 participant 2 messages May 20, 2024 – Jul 30, 2024

lore
Share & tools
lore
#0 lore raw

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: [email protected]
          Reporter: [email protected]

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’

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.
#1 lore raw

https://bugs.dpdk.org/show_bug.cgi?id=1446

Thomas Monjalon ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

         Resolution|---                         |FIXED
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #4 from Thomas Monjalon ([email protected]) --- Resolved in http://git.dpdk.org/dpdk/commit/?id=0ad961387e

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.