From: Ian Campbell <ian.campbell@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Martin Osterloh <osterlohm@ainfosec.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Current LibXL Status
Date: Thu, 19 Nov 2015 11:48:47 +0000 [thread overview]
Message-ID: <1447933727.5647.51.camel@citrix.com> (raw)
In-Reply-To: <564DB393.3070805@citrix.com>
On Thu, 2015-11-19 at 11:33 +0000, Andrew Cooper wrote:
>
> The majority of those are cases are not appropriate uses of exit().
> AFAIIR, the *only* valid use of exit() in a library is to clean up in a
> child process from a library-initiated fork().
... or (in this case) in the libxl-save-helper (separate process).
The only one I can find which isn't one of this is
in libxl__event_disaster, and that is only if the applications (or language
bindings) haven't provided a suitable disaster callback.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-11-19 11:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 18:32 Current LibXL Status Martin Osterloh
2015-11-19 9:20 ` Ian Campbell
2015-11-19 10:23 ` George Dunlap
2015-11-19 10:55 ` Andrew Cooper
2015-11-19 11:23 ` Ian Campbell
2015-11-19 11:30 ` Processed: " xen
2015-11-19 11:33 ` Andrew Cooper
2015-11-19 11:48 ` Ian Campbell [this message]
2015-11-19 11:55 ` Ian Campbell
2015-11-19 12:16 ` Ian Campbell
2015-11-20 0:30 ` Yang Hongyang
2016-02-18 17:09 ` George Dunlap
2016-02-18 17:19 ` Ian Jackson
2016-02-18 17:26 ` Ian Campbell
2016-02-18 17:40 ` George Dunlap
2016-02-18 17:24 ` Ian Campbell
2016-02-18 18:30 ` Ian Jackson
2015-11-19 15:34 ` George Dunlap
2016-02-18 17:26 ` George Dunlap
2016-02-18 17:39 ` Ian Campbell
2016-02-18 17:47 ` George Dunlap
2016-02-18 17:50 ` Ian Campbell
2016-02-18 18:15 ` libxl and malloc failure (Re: Current LibXL Status) Ian Jackson
2016-02-19 10:52 ` Ian Campbell
2016-02-19 11:00 ` Processed: " xen
2016-02-22 16:48 ` Ian Jackson
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=1447933727.5647.51.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=osterlohm@ainfosec.com \
--cc=xen-devel@lists.xen.org \
/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).