All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Orzel, Michal" <michal.orzel@amd.com>
To: Stefano Stabellini <sstabellini@kernel.org>,
	xen-devel@lists.xenproject.org
Cc: cardoe@cardoe.com, alejandro.vallejo@cloud.com,
	andrew.cooper3@citrix.com, anthony.perard@vates.tech,
	jbeulich@suse.com, julien@xen.org, roger.pau@citrix.com,
	bertrand.marquis@arm.com
Subject: Re: [PATCH] automation: enable UBSAN for debug tests
Date: Thu, 6 Feb 2025 08:46:20 +0100	[thread overview]
Message-ID: <5053348a-b02e-42b0-b35e-46f087d0d007@amd.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2502051756210.619090@ubuntu-linux-20-04-desktop>



On 06/02/2025 03:37, Stefano Stabellini wrote:
> 
> 
> automation: enable UBSAN for debug tests
> 
> Enable CONFIG_UBSAN and CONFIG_UBSAN_FATAL for the ARM64 and x86_64
> build jobs, with debug enabled, which are later used for Xen tests on
> QEMU and/or real hardware.
> 
> Signed-off-by: Stefano Stabellini <stefano.stabellini@amd.com>
Reviewed-by: Michal Orzel <michal.orzel@amd.com>

However, I do remember Julien being opposed to this approach in the past, mostly because he did not like
the idea of failing on first UB that can possibly hide next UBs (I don't see this as a problem because other
UBs will simply be found on the next pipeline or locally when testing the fix).

~Michal



  reply	other threads:[~2025-02-06  7:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-06  2:37 [PATCH] automation: enable UBSAN for debug tests Stefano Stabellini
2025-02-06  7:46 ` Orzel, Michal [this message]
2025-02-06 23:03   ` Stefano Stabellini
2025-02-07  8:28     ` Oleksii Kurochko
2025-02-07  9:27 ` Andrew Cooper
2025-02-07 23:05   ` Stefano Stabellini
2025-02-07 23:06     ` Andrew Cooper

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=5053348a-b02e-42b0-b35e-46f087d0d007@amd.com \
    --to=michal.orzel@amd.com \
    --cc=alejandro.vallejo@cloud.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@vates.tech \
    --cc=bertrand.marquis@arm.com \
    --cc=cardoe@cardoe.com \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.