From: Alex Michon <amichon@kalrayinc.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
Anatoly Burakov <anatoly.burakov@intel.com>,
dev@dpdk.org
Subject: Re: [PATCH] eal/linux: clear asan after allocation and before prefaulting
Date: Tue, 22 Oct 2024 15:37:47 +0000 [thread overview]
Message-ID: <MR1P264MB278557DDB899482D788A3246B24C2@MR1P264MB2785.FRAP264.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAJFAV8x8--X27FuOQTSupQwh=nq-rwGO+zB3=BN5gQdYgPBsGg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 774 bytes --]
Hello David,
I ran some more tests and it turns out that this issue was already fixed by this commit:
4d8bdd8b56 malloc: fix ASan handling for unmapped memory
Sorry about the noise,
Alex
________________________________
From: David Marchand <david.marchand@redhat.com>
Sent: 08 October 2024 11:36
To: Alex Michon <amichon@kalrayinc.com>
Cc: Thomas Monjalon <thomas@monjalon.net>; Anatoly Burakov <anatoly.burakov@intel.com>; dev@dpdk.org <dev@dpdk.org>
Subject: Re: [PATCH] eal/linux: clear asan after allocation and before prefaulting
On Thu, Jul 25, 2024 at 9:25 AM Alex Michon <amichon@kalrayinc.com> wrote:
>
> Prefaulting may generate asan error.
I am a bit surprised of this fix.
Could you give details on how to reproduce this issue?
--
David Marchand
[-- Attachment #2: Type: text/html, Size: 2386 bytes --]
next prev parent reply other threads:[~2024-10-22 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 8:34 Alex Michon
2024-10-08 9:36 ` David Marchand
2024-10-22 15:37 ` Alex Michon [this message]
2024-10-22 18:54 ` David Marchand
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=MR1P264MB278557DDB899482D788A3246B24C2@MR1P264MB2785.FRAP264.PROD.OUTLOOK.COM \
--to=amichon@kalrayinc.com \
--cc=anatoly.burakov@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).