From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>
Subject: Re: [PATCH 3/3] gitlab: use 'setarch -R' to workaround tsan bug
Date: Mon, 13 May 2024 13:19:58 +0200 [thread overview]
Message-ID: <be1f56af-8e2d-4f82-8641-8fbc7ea79b84@redhat.com> (raw)
In-Reply-To: <20240513111551.488088-4-berrange@redhat.com>
On 13/05/2024 13.15, Daniel P. Berrangé wrote:
> The TSAN job started failing when gitlab rolled out their latest
> release. The root cause is a change in the Google COS version used
> on shared runners. This brings a kernel running with
>
> vm.mmap_rnd_bits = 31
>
> which is incompatible with TSAN in LLVM < 18, which only supports
> upto '28'. LLVM 18 can support upto '30', and failing that will
> re-exec itself to turn off VA randomization.
>
> Our LLVM is too old for now, but we can run with 'setarch -R make ..'
> to turn off VA randomization ourselves.
>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> .gitlab-ci.d/buildtest.yml | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/.gitlab-ci.d/buildtest.yml b/.gitlab-ci.d/buildtest.yml
> index bab6194564..d864562628 100644
> --- a/.gitlab-ci.d/buildtest.yml
> +++ b/.gitlab-ci.d/buildtest.yml
> @@ -575,6 +575,9 @@ tsan-build:
> CONFIGURE_ARGS: --enable-tsan --cc=clang --cxx=clang++
> --enable-trace-backends=ust --disable-slirp
> TARGETS: x86_64-softmmu ppc64-softmmu riscv64-softmmu x86_64-linux-user
> + # Remove when we switch to a distro with clang >= 18
> + # https://github.com/google/sanitizers/issues/1716
> + MAKE: setarch -R make
Thanks for tackling this!
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2024-05-13 11:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 11:15 [PATCH 0/3] gitlab: fix failing TSAN job in CI Daniel P. Berrangé
2024-05-13 11:15 ` [PATCH 1/3] dockerfiles: add 'MAKE' env variable to remaining containers Daniel P. Berrangé
2024-05-13 11:18 ` Thomas Huth
2024-05-13 11:50 ` Philippe Mathieu-Daudé
2024-05-13 11:15 ` [PATCH 2/3] gitlab: use $MAKE instead of 'make' Daniel P. Berrangé
2024-05-13 11:18 ` Thomas Huth
2024-05-13 11:50 ` Philippe Mathieu-Daudé
2024-05-13 11:15 ` [PATCH 3/3] gitlab: use 'setarch -R' to workaround tsan bug Daniel P. Berrangé
2024-05-13 11:19 ` Thomas Huth [this message]
2024-05-13 11:22 ` Daniel P. Berrangé
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=be1f56af-8e2d-4f82-8641-8fbc7ea79b84@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=wainersm@redhat.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).