DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: bugzilla@dpdk.org
Cc: dev@dpdk.org
Subject: Re: [DPDK/core Bug 1605] lib/eal build failure with address and undefined behavior sanitizers
Date: Wed, 18 Dec 2024 08:52:45 -0800	[thread overview]
Message-ID: <20241218085245.3aabb2f8@hermes.local> (raw)
In-Reply-To: <bug-1605-3@http.bugs.dpdk.org/>

On Tue, 17 Dec 2024 20:39:12 +0000
bugzilla@dpdk.org wrote:

> https://bugs.dpdk.org/show_bug.cgi?id=1605
> 
>             Bug ID: 1605
>            Summary: lib/eal build failure with address and undefined
>                     behavior sanitizers
>            Product: DPDK
>            Version: 25.03
>           Hardware: All
>                 OS: All
>             Status: UNCONFIRMED
>           Severity: normal
>           Priority: Normal
>          Component: core
>           Assignee: dev@dpdk.org
>           Reporter: alialnu@nvidia.com
>   Target Milestone: ---
> 
> $ meson --werror -Db_sanitize=address,undefined build && ninja -C build
> [..]
> /usr/include/x86_64-linux-gnu/bits/string_fortified.h:29:10: error: writing 4
> bytes into a region of size 0 [-Werror=stringop-overflow=]
> [..]
> 
> OS: Ubuntu 22.04
> Compiler: gcc 11.2.0
> Meson: 0.61.2
> Ninja-build: 1.10.1
> 
> Build passes with "-Db_sanitize=address".
> 


Doing this found some other bugs:
[182/3218] Compiling C object drivers/libtmp_rte_bus_fslmc.a.p/bus_fslmc_portal_dpaa2_hw_dpio.c.o
../drivers/bus/fslmc/portal/dpaa2_hw_dpio.c: In function ‘dpaa2_create_dpio_device’:
../drivers/bus/fslmc/portal/dpaa2_hw_dpio.c:607:1: warning: pointer ‘dpio_dev’ used after ‘rte_free’ [-Wuse-after-free]
  607 | }
      | ^
../drivers/bus/fslmc/portal/dpaa2_hw_dpio.c:600:17: note: call to ‘rte_free’ here
  600 |                 rte_free(dpio_dev);
      |                 ^~~~~~~~~~~~~~~~~~

      reply	other threads:[~2024-12-18 16:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-17 20:39 bugzilla
2024-12-18 16:52 ` Stephen Hemminger [this message]

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=20241218085245.3aabb2f8@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=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).