From: Ilya Leoshkevich <iii@linux.ibm.com>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] tests/tcg/multiarch: add vma-pthread.c
Date: Fri, 23 Dec 2022 13:09:59 +0100 [thread overview]
Message-ID: <02e6368c68ab45dfb7527c414890fa9c251f9547.camel@linux.ibm.com> (raw)
In-Reply-To: <20221223120252.513319-1-iii@linux.ibm.com>
On Fri, 2022-12-23 at 13:02 +0100, Ilya Leoshkevich wrote:
> 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 <iii@linux.ibm.com>
> ---
> tests/tcg/multiarch/Makefile.target | 3 +
> tests/tcg/multiarch/munmap-pthread.c | 16 +--
> tests/tcg/multiarch/nop_func.h | 25 ++++
> tests/tcg/multiarch/vma-pthread.c | 185
> +++++++++++++++++++++++++++
> 4 files changed, 214 insertions(+), 15 deletions(-)
> create mode 100644 tests/tcg/multiarch/nop_func.h
> create mode 100644 tests/tcg/multiarch/vma-pthread.c
This was meant to be a reply to the bug report for [1], but apparently
I forgot to Cc: the mailing list. Copying the original message here:
---
Hi,
Wasmtime testsuite started failing randomly, complaining that
clock_gettime() returns -EFAULT. Bisect points to this commit.
I could not see anything obviously wrong here with the manual review,
and the failure was not reproducible when running individual testcases
or using strace. So I wrote a stress test (which I will post shortly),
which runs fine on the host, but reproduces the issue with qemu-user.
When run with -strace, it also triggers an assertion:
qemu-x86_64: ../accel/tcg/tb-maint.c:595:
tb_invalidate_phys_page_unwind: Assertion `pc != 0' failed.
qemu-x86_64: /home/iii/qemu/include/qemu/rcu.h:102:
rcu_read_unlock: Assertion `p_rcu_reader->depth != 0' failed.
I haven't tried analyzing what is causing all this yet, but at least
now the reproducer is small (~200LOC) and fails faster than 1s.
Best regards,
Ilya
---
[1] https://lists.gnu.org/archive/html/qemu-devel/2022-12/msg03615.html
next prev parent reply other threads:[~2022-12-23 12:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221223115348.tgfwdlektsulebxk@heavy>
2022-12-23 12:02 ` [PATCH] tests/tcg/multiarch: add vma-pthread.c Ilya Leoshkevich
2022-12-23 12:09 ` Ilya Leoshkevich [this message]
2022-12-24 15:01 ` Richard Henderson
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=02e6368c68ab45dfb7527c414890fa9c251f9547.camel@linux.ibm.com \
--to=iii@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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 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).