On 13/1/23 18:10, Alex Bennée wrote:
Peter Maydell <[email protected]> writes:
On Sat, 24 Dec 2022 at 15:19, Richard Henderson
<[email protected]> wrote:
From: Ilya Leoshkevich <[email protected]>
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 <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Richard Henderson <[email protected]>
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
Yet again:
https://gitlab.com/qemu-project/qemu/-/jobs/3608436731
Interesting those are both with plugins. I wonder if the tsan plugin
fixes in my latest tree help?
