DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Robin Jarry" <rjarry@redhat.com>
To: <dev@dpdk.org>, "Anatoly Burakov" <anatoly.burakov@intel.com>
Subject: Re: Error with --no-huge when compiled with -fsanitize=address from gcc 15
Date: Tue, 10 Jun 2025 10:15:56 +0200	[thread overview]
Message-ID: <DAIPCY7NIG04.2Z0S17M8BPQUH@redhat.com> (raw)
In-Reply-To: <D9WNYZDZHISG.3091PEP8Y34QL@redhat.com>

+Anatoly and Ferruh in direct address.

Robin Jarry, May 15, 2025 at 12:32:
> I recently updated to Fedora 42 that comes with GCC 15.
>
> When building with -fsanitize=address (libasan.so.8), it seems that
> the --no-huge mode (along with --no-shconf) fails at initialization for
> some obscure reason.
>
> "couldn't allocate memory due to IOVA exceeding limits of current DMA mask."

Hi Anatoly, Ferruh, all,

Allow me to bump this. GCC 15 has been out for quite a while now and it
seems that libasan cannot be used anymore with the DPDK memory allocator
as it is.

I have tracked the commit that introduced this warning up to 2018:

https://git.dpdk.org/dpdk/commit/?id=165c89b84538f

I would be much grateful if you could help. I don't know the internals
of libasan, but I assume it shuffles mapped memory around and it
conflicts with the DPDK allocator inner workings.

I have found this libasan commit which "could" be related:

https://github.com/llvm/llvm-project/commit/7ede1c497302

In fact, part of it was reverted a while after on macos because of
suspected breakage:

https://github.com/llvm/llvm-project/commit/4e332bba2f3a

-- 
Robin

> Driver does not carry cash.


      reply	other threads:[~2025-06-10  8:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-15 10:32 Robin Jarry
2025-06-10  8:15 ` Robin Jarry [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=DAIPCY7NIG04.2Z0S17M8BPQUH@redhat.com \
    --to=rjarry@redhat.com \
    --cc=anatoly.burakov@intel.com \
    --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).