Peter Maydell <peter.mayd...@linaro.org> writes:
> On Sat, 24 Dec 2022 at 15:19, Richard Henderson > <richard.hender...@linaro.org> wrote: >> >> From: Ilya Leoshkevich <i...@linux.ibm.com> >> >> Add a test that locklessly changes and exercises page protection bits >> from various threads. This helps catch race conditions in the VMA >> handling. >> >> Signed-off-by: Ilya Leoshkevich <i...@linux.ibm.com> >> Message-Id: <20221223120252.513319-1-...@linux.ibm.com> >> Signed-off-by: Richard Henderson <richard.hender...@linaro.org> > > I've noticed that this newly added vma-pthread test seems to > be flaky. Here's an example from a clang-user job: > https://gitlab.com/qemu-project/qemu/-/jobs/3600385176 > > TEST vma-pthread-with-libbb.so on aarch64 > fail indirect write 0x5500b1eff0 (Bad address) > timeout: the monitored command dumped core > Aborted > make[1]: *** [Makefile:173: run-plugin-vma-pthread-with-libbb.so] Error 134 > > and another from a few days earlier: > https://gitlab.com/qemu-project/qemu/-/jobs/3572970612 > > TEST vma-pthread-with-libsyscall.so on s390x > fail indirect read 0x4000999000 (Bad address) > timeout: the monitored command dumped core > Aborted > make[1]: *** [Makefile:173: run-plugin-vma-pthread-with-libsyscall.so] Error > 134 > > thanks > -- PMM Interesting those are both with plugins. I wonder if the tsan plugin fixes in my latest tree help? -- Alex Bennée Virtualisation Tech Lead @ Linaro