All of lore.kernel.org
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: Mao Chuan Li <maochuan@linux.vnet.ibm.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Michael Mueller <mimu@linux.vnet.ibm.com>,
	Alexander Graf <agraf@suse.de>,
	qemu-devel <qemu-devel@nongnu.org>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Cornelia Huck <cornelia.huck@de.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v1 RFC 4/9] qemu-iotests: fix test 039
Date: Thu, 20 Nov 2014 09:45:55 +0100	[thread overview]
Message-ID: <546DAA43.1090400@redhat.com> (raw)
In-Reply-To: <1416470936.23362.1.camel@maoLaptop.cn.ibm.com>

On 2014-11-20 at 09:08, Mao Chuan Li wrote:
> The intention is to disable the core dump, if there is another way we
> can achieve that, switching to root is not necessary. Any other
> alternative way?  Thanks!
>
> Mao Chuan Li

Hi,

I cannot think of a way; on the other hand, I don't think disabling the 
core dump is necessary either. Simply filtering out '(core dumped) ' is 
not pretty but still suffices for me (we can put that into a filter 
function in common.filter and if other people see other messages for a 
core dump, they can expand that list).

If we really want to disable core dumps, we should change qemu-io not to 
use abort() on -c abort (raise(SIGKILL) seems like a good alternative to 
me); or, alternatively, introduce a new command 'kill' which then does 
raise(SIGKILL) so we don't have to break compatibility.

Max

       reply	other threads:[~2014-11-20  8:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1416470936.23362.1.camel@maoLaptop.cn.ibm.com>
2014-11-20  8:45 ` Max Reitz [this message]
2014-11-13 10:36 [Qemu-devel] [PATCH v1 RFC 0/9] Update tests/qemu-iotests cases for multi-platform support Mao Chuan Li
2014-11-13 10:36 ` [Qemu-devel] [PATCH v1 RFC 4/9] qemu-iotests: fix test 039 Mao Chuan Li
2014-11-13 15:54   ` Max Reitz
2014-11-25 18:07   ` 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=546DAA43.1090400@redhat.com \
    --to=mreitz@redhat.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=cornelia.huck@de.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.