From: Aaron Conole <aconole@redhat.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, john.mcnamara@intel.com,
Michael Santana <maicolgabriel@hotmail.com>
Subject: Re: [PATCH v2 2/2] ci: build some job with ASan
Date: Tue, 10 May 2022 15:22:45 -0400 [thread overview]
Message-ID: <f7twnetp4ze.fsf@redhat.com> (raw)
In-Reply-To: <20220505092952.11818-3-david.marchand@redhat.com> (David Marchand's message of "Thu, 5 May 2022 11:29:52 +0200")
David Marchand <david.marchand@redhat.com> writes:
> Enable ASan, this can greatly help identify leaks and buffer overflows.
> Running unit tests relying on multiprocess is unreliable with ASan
> enabled, so skip them.
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
> Changes since v1:
> - reinstated table_autotest in "ASan-safe" list of ut,
This is great!
Acked-by: Aaron Conole <aconole@redhat.com>
next prev parent reply other threads:[~2022-05-10 19:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 17:31 [PATCH 0/3] Enable ASan in GHA David Marchand
2022-04-15 17:31 ` [PATCH 1/3] test/mem: disable ASan when accessing unallocated mem David Marchand
2022-04-20 14:48 ` Burakov, Anatoly
2022-04-15 17:31 ` [PATCH 2/3] mem: fix ASan shadow for remapped memory segments David Marchand
2022-04-20 14:47 ` Burakov, Anatoly
2022-04-21 9:37 ` David Marchand
2022-04-21 9:50 ` David Marchand
2022-04-21 13:18 ` Burakov, Anatoly
2022-04-26 12:54 ` Burakov, Anatoly
2022-04-26 14:15 ` David Marchand
2022-04-26 16:07 ` Burakov, Anatoly
2022-04-27 15:32 ` Burakov, Anatoly
2022-04-15 17:31 ` [PATCH 3/3] ci: build some job with ASan David Marchand
2022-05-05 9:29 ` [PATCH v2 0/2] Enable ASan in GHA David Marchand
2022-05-05 9:29 ` [PATCH v2 1/2] test/mem: disable ASan when accessing unallocated mem David Marchand
2022-05-05 9:29 ` [PATCH v2 2/2] ci: build some job with ASan David Marchand
2022-05-10 19:22 ` Aaron Conole [this message]
2022-05-11 12:01 ` [PATCH v2 0/2] Enable ASan in GHA 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=f7twnetp4ze.fsf@redhat.com \
--to=aconole@redhat.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=maicolgabriel@hotmail.com \
/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).