From: Max Reitz <mreitz@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
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>,
qemu-devel@nongnu.org, "Stefan Hajnoczi" <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/3] iotests: Fix test 039
Date: Tue, 25 Nov 2014 13:29:29 +0100 [thread overview]
Message-ID: <54747629.8060709@redhat.com> (raw)
In-Reply-To: <87k32jii7e.fsf@blackfin.pond.sub.org>
On 2014-11-25 at 13:21, Markus Armbruster wrote:
> Max Reitz <mreitz@redhat.com> writes:
>
>> Test 039 used to fail
> I'm confused: "used to" suggests it doesn't anymore, but you sending a
> patches strongly suggests something's broken.
Well, it used to fail before this series. :-P
You're right, this sounds bad. Currently, 039 does fail, at least on any
system with a /proc/sys/kernel/core_pattern passing the dump to another
program. After this series, it does no longer.
>> because qemu-io -c abort may generate core dumps
>> even with ulimit -c 0 (and the output then contains "(core dumped)").
> How?
See the patches[1][2] by Mao Chuan Li. If /proc/sys/kernel/core_pattern
passes the dump to another program, ulimit -c 0 does not matter.
[1] http://lists.nongnu.org/archive/html/qemu-devel/2014-11/msg02092.html
[2] http://lists.nongnu.org/archive/html/qemu-devel/2014-11/msg02093.html
The problem with those patches is that they require access to
/proc/sys/kernel/core_pattern. I don't like having to run the iotests as
root.
Max
next prev parent reply other threads:[~2014-11-25 12:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 10:09 [Qemu-devel] [PATCH 0/3] iotests: Fix test 039 Max Reitz
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 [this message]
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=54747629.8060709@redhat.com \
--to=mreitz@redhat.com \
--cc=armbru@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).