From: Max Reitz <mreitz@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Kevin Wolf" <kwolf@redhat.com>, "Fam Zheng" <famz@redhat.com>,
"Michael Müller" <mimu@linux.vnet.ibm.com>,
"Mao Chuan Li" <maochuan@linux.vnet.ibm.com>,
"Max Reitz" <mreitz@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>
Subject: [Qemu-devel] [PATCH 0/3] iotests: Fix test 039
Date: Tue, 25 Nov 2014 11:09:35 +0100 [thread overview]
Message-ID: <1416910178-5088-1-git-send-email-mreitz@redhat.com> (raw)
Test 039 used to fail because qemu-io -c abort may generate core dumps
even with ulimit -c 0 (and the output then contains "(core dumped)").
Fix this by adding an option to the "abort" command which allows
specifying a signal number to raise(). Using SIGKILL for example does
not result in a core dump, but it still badly crashes qemu-io (as
desired).
I am sending this series because we need all tests to work before adding
the check-block target to "make check" (which we will hopefully do
soon).
Max Reitz (3):
qemu-io: Let -c abort raise any signal
iotests: Filter for "Killed" in qemu-io output
iotests: Fix test 039
qemu-io-cmds.c | 59 ++++++++++++++++++++++++++++++++++++++--
tests/qemu-iotests/039 | 12 ++++----
tests/qemu-iotests/039.out | 6 ++--
tests/qemu-iotests/common.filter | 2 +-
4 files changed, 67 insertions(+), 12 deletions(-)
--
1.9.3
next reply other threads:[~2014-11-25 10:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 10:09 Max Reitz [this message]
2014-11-25 10:09 ` [Qemu-devel] [PATCH 1/3] qemu-io: Let -c abort raise any signal Max Reitz
2014-11-25 13:19 ` Markus Armbruster
2014-11-25 13:31 ` Max Reitz
2014-11-25 10:09 ` [Qemu-devel] [PATCH 2/3] iotests: Filter for "Killed" in qemu-io output Max Reitz
2014-11-25 13:05 ` Markus Armbruster
2014-11-25 13:06 ` Max Reitz
2014-11-25 10:09 ` [Qemu-devel] [PATCH 3/3] iotests: Fix test 039 Max Reitz
2014-11-25 12:21 ` [Qemu-devel] [PATCH 0/3] " Markus Armbruster
2014-11-25 12:29 ` Max Reitz
2014-11-25 13:20 ` Markus Armbruster
2014-11-25 13:22 ` Max Reitz
2014-11-25 13:48 ` Markus Armbruster
2014-11-25 13:50 ` Max Reitz
2014-11-25 14:04 ` Markus Armbruster
2014-11-25 16:53 ` Michael Mueller
2014-11-25 16:48 ` Michael Mueller
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=1416910178-5088-1-git-send-email-mreitz@redhat.com \
--to=mreitz@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=maochuan@linux.vnet.ibm.com \
--cc=mimu@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).