DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Robin Jarry" <rjarry@redhat.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>, <dev@dpdk.org>
Subject: Re: Error with --no-huge when compiled with -fsanitize=address from gcc 15
Date: Thu, 04 Sep 2025 16:49:15 +0200	[thread overview]
Message-ID: <DCK3KYFOL7EF.1CBE546ZJUS04@redhat.com> (raw)
In-Reply-To: <9d2e0536-98af-4532-aa57-dd1605d6e070@intel.com>

Hey Anatoly,

Burakov, Anatoly, Sep 04, 2025 at 16:35:
> I have been trying to reproduce this but I'm unable to. I run some old 
> CentOS so I built GCC15 manually and tried reproducing with that. The 
> version I'm using is 15.2, could you please retest with latest GCC15 and 
> see if it was fixed?

I am running on Fedora 42 that has GCC 15.2.1 and the problem persists.

> (if not, I'll try to get a more recent distro and reproduce again)
>
> The DMA mask checking you're referring to is there for cases where e.g. 
> in a VM the emulated IOMMU will not have full address width (39 bits was 
> common at the time), and thus we couldn't use the full VA space for IOVA 
> addressing, and had to resort to using real physical addresses (because 
> kernel ensure those are to be within support range of IOMMU). Were you 
> running this test in a VM, by any chance?

No I am running on a physical machine. I tested again without --no-huge
and 2M/1G huge pages, and the issue persists as well.

I tried both as root, and as a regular user.

-- 
Robin

> Formatted to fit your screen.


  reply	other threads:[~2025-09-04 14:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-15 10:32 Robin Jarry
2025-06-10  8:15 ` Robin Jarry
2025-09-04 14:35   ` Burakov, Anatoly
2025-09-04 14:49     ` Robin Jarry [this message]
2025-09-05  9:17       ` Burakov, Anatoly

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=DCK3KYFOL7EF.1CBE546ZJUS04@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).