From: Stefan Hajnoczi <stefanha@gmail.com>
To: Max Reitz <mreitz@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>, "Fam Zheng" <famz@redhat.com>,
"Michael Müller" <mimu@linux.vnet.ibm.com>,
"Markus Armbruster" <armbru@redhat.com>,
qemu-devel@nongnu.org, "Stefan Hajnoczi" <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 0/3] iotests: Fix test 039
Date: Fri, 12 Dec 2014 16:35:46 +0000 [thread overview]
Message-ID: <20141212163546.GA12762@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1418032092-16813-1-git-send-email-mreitz@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2088 bytes --]
On Mon, Dec 08, 2014 at 10:48:09AM +0100, Max Reitz wrote:
> 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 a new qemu-io command "sigraise" which invokes
> raise(). Using this command to raise 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).
>
>
> v3:
> - Patch 1:
> - s/allows to raise/allows raising/ [Eric]
> - %s/Unix signal/signal/g [Markus]
> - Use SIGTERM instead of SIGKILL in the example, and don't hardcode
> its value [Markus]
> - Patch 3:
> - Fix commit message (should have been "sigraise 9" instead of
> "abort -S 9", and now it's "sigraise $(kill -l KILL)") [Fam]
> - As hinted above, use "sigraise $(kill -l KILL)" instead of
> hardcoding the value 9 for SIGKILL [Markus]
>
>
> git-backport-diff against v2:
>
> Key:
> [----] : patches are identical
> [####] : number of functional differences between upstream/downstream patch
> [down] : patch is downstream-only
> The flags [FC] indicate (F)unctional and (C)ontextual differences, respectively
>
> 001/3:[0008] [FC] 'qemu-io: Add sigraise command'
> 002/3:[----] [--] 'iotests: Filter for "Killed" in qemu-io output'
> 003/3:[0012] [FC] 'iotests: Fix test 039'
>
>
> Max Reitz (3):
> qemu-io: Add sigraise command
> iotests: Filter for "Killed" in qemu-io output
> iotests: Fix test 039
>
> qemu-io-cmds.c | 46 ++++++++++++++++++++++++++++++++++++++++
> tests/qemu-iotests/039 | 18 +++++++++++-----
> tests/qemu-iotests/039.out | 6 +++---
> tests/qemu-iotests/common.filter | 2 +-
> 4 files changed, 63 insertions(+), 9 deletions(-)
>
> --
> 1.9.3
>
>
Thanks, applied to my block-next tree:
https://github.com/stefanha/qemu/commits/block-next
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2014-12-12 16:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 9:48 [Qemu-devel] [PATCH v3 0/3] iotests: Fix test 039 Max Reitz
2014-12-08 9:48 ` [Qemu-devel] [PATCH v3 1/3] qemu-io: Add sigraise command Max Reitz
2014-12-08 10:34 ` Fam Zheng
2014-12-08 9:48 ` [Qemu-devel] [PATCH v3 2/3] iotests: Filter for "Killed" in qemu-io output Max Reitz
2014-12-08 9:48 ` [Qemu-devel] [PATCH v3 3/3] iotests: Fix test 039 Max Reitz
2014-12-08 10:36 ` Fam Zheng
2014-12-12 16:35 ` Stefan Hajnoczi [this message]
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=20141212163546.GA12762@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=armbru@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mimu@linux.vnet.ibm.com \
--cc=mreitz@redhat.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).