From: Ilya Leoshkevich <iii@linux.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Eduardo Habkost <ehabkost@redhat.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
qemu-devel@nongnu.org, Ilya Leoshkevich <iii@linux.ibm.com>
Subject: [PATCH v2 0/2] target/i386: Make sure that vsyscall's tb->size != 0
Date: Wed, 19 May 2021 06:57:36 +0200 [thread overview]
Message-ID: <20210519045738.1335210-1-iii@linux.ibm.com> (raw)
This series for the s390-next tree fixes [1]. Patch 1 is the fix, patch
2 is the new test to avoid similar regressions in the future.
[1] https://lists.nongnu.org/archive/html/qemu-devel/2021-05/msg02962.html
v1: https://lists.gnu.org/archive/html/qemu-devel/2021-05/msg03219.html
v1 -> v2: Fixed a problem with compiling the new test on centos7. `make
docker-all-tests` does not spot any other issues with the
updated patch (it does fail though: a number of iotests have
problems, there is a build problem with musl, etc, but this
all happens without the patch too).
Ilya Leoshkevich (2):
target/i386: Make sure that vsyscall's tb->size != 0
tests/tcg/x86_64: add vsyscall smoke test
target/i386/tcg/translate.c | 1 +
tests/tcg/x86_64/Makefile.target | 6 +++++-
tests/tcg/x86_64/vsyscall.c | 12 ++++++++++++
3 files changed, 18 insertions(+), 1 deletion(-)
create mode 100644 tests/tcg/x86_64/vsyscall.c
--
2.31.1
next reply other threads:[~2021-05-19 4:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 4:57 Ilya Leoshkevich [this message]
2021-05-19 4:57 ` [PATCH v2 1/2] target/i386: Make sure that vsyscall's tb->size != 0 Ilya Leoshkevich
2021-05-19 4:57 ` [PATCH v2 2/2] tests/tcg/x86_64: add vsyscall smoke test Ilya Leoshkevich
2021-05-19 16:42 ` Richard Henderson
2021-05-19 11:14 ` [PATCH v2 0/2] target/i386: Make sure that vsyscall's tb->size != 0 Cornelia Huck
2021-05-19 17:13 ` Cornelia Huck
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=20210519045738.1335210-1-iii@linux.ibm.com \
--to=iii@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).