From: "Daniel P. Berrange" <berrange@redhat.com>
To: Zhi Yong Wu <zwu.kernel@gmail.com>
Cc: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH] oslib: make error handling more reasonable
Date: Fri, 10 Feb 2012 14:41:15 +0000 [thread overview]
Message-ID: <20120210144115.GI2914@redhat.com> (raw)
In-Reply-To: <1328884453-1067-1-git-send-email-zwu.kernel@gmail.com>
On Fri, Feb 10, 2012 at 10:34:13PM +0800, Zhi Yong Wu wrote:
> From: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
>
> Signed-off-by: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
> ---
> oslib-posix.c | 4 ++--
> oslib-win32.c | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/oslib-posix.c b/oslib-posix.c
> index b6a3c7f..f978d56 100644
> --- a/oslib-posix.c
> +++ b/oslib-posix.c
> @@ -80,7 +80,7 @@ void *qemu_oom_check(void *ptr)
> {
> if (ptr == NULL) {
> fprintf(stderr, "Failed to allocate memory: %s\n", strerror(errno));
> - abort();
> + exit(EXIT_FAILURE);
exit() will call any atexit()/on_exit() handlers, as well as trying
to flush I/O streams. Any of these actions may require further
memory allocations, which will likely fail, or worse cause this
code to re-enter itself if an atexit() handler calls qemu_malloc
The only option other than abort(), is to use _Exit() which
doesn't try to run cleanup handlers.
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2012-02-10 14:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 14:34 [Qemu-devel] [PATCH] oslib: make error handling more reasonable Zhi Yong Wu
2012-02-10 14:41 ` Daniel P. Berrange [this message]
2012-02-10 15:13 ` Zhi Yong Wu
2012-02-10 15:53 ` Stefan Weil
2012-02-13 2:37 ` Zhi Yong Wu
2012-02-13 6:29 ` Stefan Weil
2012-02-13 11:16 ` Stefan Hajnoczi
2012-02-14 12:46 ` Anthony Liguori
2012-02-14 12:45 ` Anthony Liguori
2012-02-13 14:04 ` Markus Armbruster
2012-02-13 14:30 ` Peter Maydell
2012-02-14 12:42 ` Paul Brook
2012-02-14 12:46 ` Daniel P. Berrange
2012-02-14 13:07 ` Paul Brook
2012-02-14 12:47 ` Anthony Liguori
2012-02-10 18:35 ` Eric Blake
2012-02-13 2:42 ` Zhi Yong Wu
2012-02-13 9:17 ` Daniel P. Berrange
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=20120210144115.GI2914@redhat.com \
--to=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.com \
--cc=wuzhy@linux.vnet.ibm.com \
--cc=zwu.kernel@gmail.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).